C33 832041 Saverne – Sélestat

View line C33

Saverne 21:19 → Sélestat 22:50 Mon, Tue, Wed, Thu, Fri, Sat 1 h 31 min · 21 stops SNCF

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 21:19 from Saverne · Wed 18 Nov

Next departure 21:19 today · Saverne
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
87%
61/70 runs under 3 min
RT coverage: 70 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 1 Oct Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8721413 +20 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Sélestat +5 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Sélestat +5 min
  • Fri 6 Nov Max en route +5 min · last fix heading to Sélestat +5 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Sélestat +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 61
  • 3–10 min 11% · 8
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 85% M n=13
  • 91% T n=11
  • 100% W n=10
  • 90% T n=10
  • 85% F n=13
  • 77% S n=13
  • — S n=0

Stops and timetable

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

Last 90 days, 70 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
21:19on time on time
21:23 / 21:24≈ on time ≈ on time
21:27 / 21:28≈ on time ≈ on time
21:31 / 21:32≈ on time ≈ +1 min
21:35 / 21:36≈ on time ≈ +1 min
21:38 / 21:39≈ on time ≈ +1 min
21:42 / 21:43≈ on time ≈ +1 min
21:47≈ on time ≈ +2 min
21:49 / 21:50≈ on time ≈ +2 min
21:54 / 21:55≈ on time ≈ +2 min
22:03 / 22:07≈ on time ≈ +2 min
22:13≈ on time ≈ +3 min
22:15 / 22:16≈ on time ≈ +3 min
22:19≈ on time ≈ +3 min
22:22≈ on time ≈ +3 min
22:26 / 22:27≈ on time ≈ +4 min
22:30≈ on time ≈ +4 min
22:34 / 22:35≈ on time ≈ +4 min
22:39 / 22:40≈ on time ≈ +4 min
22:44 / 22:45≈ on time ≈ +5 min
22:50on time +5 min

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
Tue 17 NovSélestat 22:490 min—
Mon 16 NovSélestat 22:490 min—
Sat 14 NovSélestat 22:490 min—
Fri 13 NovSélestat 22:520 min—
Thu 12 NovSélestat 22:490 min—
Tue 10 NovSélestat 22:490 min—
Mon 9 NovSélestat 22:54+5 min+5 min
Sat 7 NovSélestat 22:54+5 min+5 min
Fri 6 NovSélestat 22:54+5 min+5 min
Wed 4 NovSélestat 22:490 min—
Tue 3 NovSélestat 22:500 min—
Mon 2 NovSélestat 22:490 min—
Sat 31 OctSélestat 22:510 min—
Fri 30 OctSélestat 22:510 min—
Thu 29 OctSélestat 22:510 min—
Wed 28 OctSélestat 22:510 min—
Tue 27 OctSélestat 22:510 min—
Mon 26 OctSélestat 22:520 min—
Sat 24 OctSélestat 22:510 min—
Fri 23 OctSélestat 22:520 min—
Thu 22 OctSélestat 22:510 min—
Wed 21 OctSélestat 22:510 min—
Tue 20 OctSélestat 22:510 min—
Mon 19 OctSélestat 22:56+5 min+5 min
Sat 17 OctSélestat 22:500 min—
Fri 16 OctSélestat 22:510 min—
Thu 15 OctSélestat 22:510 min—
Wed 14 OctSélestat 22:510 min—
Tue 13 OctSélestat 22:510 min—
Mon 12 OctSélestat 22:510 min—