K200 832325 Strasbourg – Mulhouse

View line K200

Strasbourg 22:51 → Mulhouse 23:44 Sun 0 h 53 min · 4 stops SNCF

It does not run today

Last recorded run: Sunday 15 November +5 min

Next service: Sunday 22:51 from Strasbourg · Sun 22 Nov

Next departure 22:51 Sunday · Strasbourg
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
57%
8/14 runs under 3 min
RT coverage: 14 full · 0 partial · 6 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Sun 4 Oct Max en route +50 min · last fix heading to StopPoint:OCETrain TE~cef89d1b +45 min
  • Sun 27 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8718206 +10 min
  • Sun 13 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8718206 +10 min
  • Sun 6 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8718206 +10 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Mulhouse +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 57% · 8
  • 3–10 min 14% · 2
  • 10–30 min 21% · 3
  • 30+ min 7% · 1

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • — S n=0
  • 54% S n=13

Stops and timetable

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

Last 90 days, 14 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
22:51on time +10 min
23:10 / 23:12≈ +1 min ≈ +10 min
23:23 / 23:25≈ +1 min ≈ +10 min
23:44on time +10 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
Sun 15 NovMulhouse 23:49+5 min+5 min
Wed 11 NovMulhouse 23:440 min—
Sun 8 NovMulhouse 23:440 min—
Sun 1 NovMulhouse 23:440 min+5 min
Sun 25 OctMulhouse 23:450 min—
Sun 18 OctMulhouse 23:450 min—
Sun 11 OctMulhouse 23:450 min—
Sun 4 OctStopPoint:OCETrain TE~cef89d1b 00:30+45 min+50 min
Wed 30 SeptStopPoint:OCETrain TER-8718206 23:43No data—
Sun 27 SeptStopPoint:OCETrain TER-8718206 23:44+10 min+10 min
Wed 23 SeptStopPoint:OCETrain TER-8718206 23:43No data—
Sun 20 SeptStopPoint:OCETrain TER-8718206 23:44+5 min+5 min
Wed 16 SeptStopPoint:OCETrain TER-8718206 23:43No data—
Sun 13 SeptStopPoint:OCETrain TER-8718206 23:43+10 min+10 min
Wed 9 SeptStopPoint:OCETrain TER-8718206 23:43No data—
Sun 6 SeptStopPoint:OCETrain TER-8718206 23:43+10 min+10 min
Wed 2 SeptStopPoint:OCETrain TER-8718206 23:43No data—
Sun 30 AugStopPoint:OCETrain TER-8718206 23:430 min—
Wed 26 AugStopPoint:OCETrain TER-8718206 23:43No data—
Sun 23 AugStopPoint:OCETrain TER-8718206 23:430 min—