C33 832024 Sélestat → Saverne

View line C33

Sélestat 15:42 → Saverne 17:08 Mon, Tue, Wed, Thu, Fri 1 h 26 min · 18 stops SNCF

TER 832024 Sélestat–Saverne: final delay under 3 min on 17 of its 19 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:35 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 15:42 from Sélestat · Mon 23 Nov

Next departure 15:42 tomorrow · Sélestat
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 33 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Saverne, in minutes. One bar per run.

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

Worst days

  • Wed 28 Oct Max en route +10 min · last fix heading to Saverne +10 min
  • Thu 5 Nov Max en route +5 min · last fix heading to Saverne +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Saverne +5 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Saverne +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 9% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
15:42on time on time
15:51 / 15:52≈ on time ≈ on time
15:56 / 15:57≈ on time ≈ +1 min
16:00 / 16:01≈ on time ≈ +1 min
16:04 / 16:05≈ on time ≈ +1 min
16:08 / 16:09≈ on time ≈ +1 min
16:11 / 16:12≈ on time ≈ +1 min
16:20 / 16:24≈ on time ≈ +2 min
16:31 / 16:32≈ on time ≈ +2 min
16:36 / 16:37≈ on time ≈ +3 min
16:39 / 16:40≈ on time ≈ +3 min
16:44 / 16:45≈ on time ≈ +3 min
16:47 / 16:48≈ on time ≈ +3 min
16:50 / 16:51≈ on time ≈ +3 min
16:55 / 16:56≈ on time ≈ +4 min
16:58 / 16:59≈ on time ≈ +4 min
17:03≈ on time ≈ +4 min
17:08on time +4 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
Fri 20 NovSaverne 17:090 min—
Thu 19 NovSaverne 17:090 min—
Wed 18 NovSaverne 17:09+1 min+1 min
Tue 17 NovSaverne 17:090 min—
Mon 16 NovSaverne 17:090 min—
Fri 13 NovSaverne 17:100 min—
Thu 12 NovSaverne 17:090 min—
Tue 10 NovSaverne 17:090 min—
Mon 9 NovSaverne 17:090 min—
Fri 6 NovSaverne 17:090 min—
Thu 5 NovSaverne 17:14+5 min+5 min
Wed 4 NovSaverne 17:090 min—
Tue 3 NovSaverne 17:100 min—
Mon 2 NovSaverne 17:090 min—
Fri 30 OctSaverne 17:090 min—
Thu 29 OctSaverne 17:090 min—
Wed 28 OctSaverne 17:19+10 min+10 min
Tue 27 OctSaverne 17:090 min—
Mon 26 OctSaverne 17:100 min—
Thu 22 OctSaverne 17:100 min—
Wed 21 OctSaverne 17:090 min—
Tue 20 OctSaverne 17:14+5 min+5 min
Mon 19 OctSaverne 17:100 min—
Fri 16 OctSaverne 17:090 min—
Thu 15 OctSaverne 17:090 min—
Wed 14 OctSaverne 17:090 min—
Tue 13 OctSaverne 17:090 min—
Mon 12 OctSaverne 17:090 min—
Fri 9 OctSaverne 17:090 min—
Thu 8 OctSaverne 17:090 min—