C33 832017 Saverne – Sélestat

View line C33

Saverne 11:19 → Sélestat 12:49 Daily 1 h 30 min · 21 stops SNCF

✓ Today’s run finished

Today it reached Sélestat at 12:49 0 min

  1. Saverne11:19
  2. Wilwisheim11:31
  3. Brumath11:46
  4. Strasbourg12:03
  5. Fegersheim - Lipsheim12:19
  6. Benfeld12:35
  7. Sélestat12:49

Next service: tomorrow 11:19 from Saverne · Sun 15 Nov

Next departure 11:19 tomorrow · Saverne
On-time · 30 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
91%
42/46 runs under 3 min
RT coverage: 45 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Sélestat, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +40 min · last fix heading to Sélestat +20 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Sélestat +5 min
  • Sat 24 Oct Max en route +5 min · last fix heading to Sélestat +5 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Sélestat +5 min

Distribution · 90 days

46 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 91% · 42
  • 3–10 min 7% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 86% W n=7
  • 100% T n=6
  • 86% F n=7
  • 83% S n=6
  • 83% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (21 stops).

Last 90 days, 46 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
11:19on time on time
11:23 / 11:24≈ on time ≈ on time
11:27 / 11:28≈ on time ≈ on time
11:31≈ on time ≈ on time
11:35 / 11:36≈ on time ≈ +1 min
11:38 / 11:39≈ on time ≈ +1 min
11:42 / 11:43≈ on time ≈ +1 min
11:46 / 11:47≈ on time ≈ +1 min
11:49≈ on time ≈ +1 min
11:53 / 11:54≈ on time ≈ +1 min
12:03 / 12:07≈ on time ≈ +1 min
12:13 / 12:14≈ on time ≈ +2 min
12:15 / 12:16≈ on time ≈ +2 min
12:19≈ on time ≈ +2 min
12:22 / 12:23≈ on time ≈ +2 min
12:26 / 12:27≈ on time ≈ +2 min
12:30 / 12:31≈ on time ≈ +1 min
12:35 / 12:36≈ on time ≈ +1 min
12:40 / 12:41≈ on time ≈ +1 min
12:44≈ on time ≈ on time
12:49on time on time

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Sat 14 NovSélestat 12:490 min—
Fri 13 NovSélestat 12:490 min—
Thu 12 NovSélestat 12:490 min—
Wed 11 NovSélestat 12:490 min—
Tue 10 NovSélestat 12:490 min—
Mon 9 NovSélestat 12:490 min—
Sun 8 NovSélestat 12:490 min—
Sat 7 NovSélestat 12:490 min—
Fri 6 NovSélestat 12:490 min—
Wed 4 NovSélestat 12:54+5 min+5 min
Tue 3 NovSélestat 12:500 min—
Mon 2 NovSélestat 12:490 min—
Sun 1 NovSélestat 12:500 min—
Sat 31 OctSélestat 12:500 min—
Fri 30 OctSélestat 12:500 min—
Thu 29 OctSélestat 12:500 min—
Wed 28 OctSélestat 12:500 min—
Tue 27 OctSélestat 12:500 min—
Mon 26 OctSélestat 12:500 min—
Sun 25 OctSélestat 12:500 min—
Sat 24 OctSélestat 12:55+5 min+5 min
Fri 23 OctSélestat 12:500 min—
Thu 22 OctSélestat 12:500 min—
Wed 21 OctSélestat 12:500 min—
Tue 20 OctSélestat 12:510 min—
Mon 19 OctSélestat 12:500 min—
Sun 18 OctSélestat 12:55+5 min+5 min
Sat 17 OctSélestat 12:500 min—
Fri 16 OctSélestat 12:500 min—
Thu 15 OctSélestat 12:500 min—