P14 832752 Mulhouse – Kruth

View line P14

Mulhouse 05:34 → Kruth 06:31 Mon, Tue, Wed, Thu, Fri 0 h 57 min · 13 stops SNCF

It does not run today

Last recorded run: Friday 6 November +15 min

Next service: tomorrow 05:34 from Mulhouse · Mon 9 Nov

Next departure 05:34 tomorrow · Mulhouse
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Kruth, 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 6 Nov Max en route +15 min · last fix heading to Kruth +15 min
  • Mon 12 Oct Max en route +15 min · last fix heading to Kruth +9 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 86% · 12
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 67% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
05:34on time on time
05:37≈ on time ≈ +1 min
05:40 / 05:41≈ on time ≈ +1 min
05:45 / 05:46≈ on time ≈ +2 min
05:52 / 05:53≈ on time ≈ +3 min
05:56 / 05:57≈ on time ≈ +4 min
05:59≈ on time ≈ +5 min
06:01 / 06:03≈ on time ≈ +5 min
06:04≈ on time ≈ +5 min
06:06 / 06:09≈ on time ≈ +5 min
06:12 / 06:13≈ on time ≈ +5 min
06:15 / 06:19≈ on time ≈ +6 min
06:31on time +6 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 6 NovKruth 06:44+15 min+15 min
Wed 4 NovKruth 06:320 min—
Tue 3 NovKruth 06:320 min—
Mon 2 NovKruth 06:320 min—
Fri 16 OctKruth 06:320 min—
Thu 15 OctKruth 06:320 min—
Wed 14 OctKruth 06:320 min—
Tue 13 OctKruth 06:320 min—
Mon 12 OctKruth 06:41+9 min+15 min
Fri 9 OctKruth 06:320 min—
Thu 8 OctKruth 06:330 min—
Wed 7 OctKruth 06:320 min—
Tue 6 OctKruth 06:320 min—
Mon 5 OctStopPoint:OCETrain TE~92f5be07 06:330 min—