C12 96116 Saint-Louis (Haut-Rhin) – Mulhouse

View line C12

Saint-Louis (Haut-Rhin) 12:47 → Mulhouse 13:10 Daily 0 h 23 min · 7 stops SNCF

Running now · updated 12:59

Position estimated from the timetable

Between Sierentz and Habsheim No data

Estimated arrival at Mulhouse 13:10 · 117 km/h

  1. Saint-Louis (Haut-Rhin)12:47
  2. Saint-Louis la Chaussée12:49
  3. Bartenheim12:53
  4. Sierentz12:56
  5. Habsheim13:02
  6. Rixheim13:05
  7. Mulhouse13:10
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
89%
39/44 runs under 3 min
RT coverage: 44 full · 0 partial · 10 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: +5 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

  • Fri 30 Oct Max en route +25 min · last fix heading to Mulhouse +25 min
  • Tue 10 Nov Max en route +10 min · last fix heading to Mulhouse +10 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Mulhouse +10 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Mulhouse +5 min
  • Thu 1 Oct Max en route +5 min · last fix heading to Rixheim +5 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 84% · 37
  • 3–10 min 5% · 2
  • 10–30 min 7% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 88% T n=8
  • 86% W n=7
  • 33% T n=3
  • 88% F n=8
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 44 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 10Today
12:47on time on timePassed
12:49 / 12:50≈ on time ≈ on timePassed
12:53 / 12:54≈ on time ≈ +1 minPassed
12:56 / 12:57≈ on time ≈ +1 minPassed
13:02 / 13:03≈ on time ≈ +2 minNext
13:05≈ on time ≈ +3 min
13:10on 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
Mon 16 NovSierentz 12:54Partial coverageNo data—
Sun 15 NovMulhouse 13:090 min—
Sat 14 NovMulhouse 13:090 min—
Fri 13 NovMulhouse 13:090 min—
Thu 12 NovMulhouse 13:09No data—
Wed 11 NovMulhouse 13:14+5 min+5 min
Tue 10 NovMulhouse 13:19+10 min+10 min
Mon 9 NovMulhouse 13:090 min—
Sun 8 NovMulhouse 13:090 min—
Sat 7 NovMulhouse 13:090 min—
Fri 6 NovMulhouse 13:090 min—
Thu 5 NovMulhouse 13:09No data—
Wed 4 NovMulhouse 13:090 min—
Tue 3 NovMulhouse 13:090 min—
Mon 2 NovMulhouse 13:09No data—
Sun 1 NovMulhouse 13:110 min—
Sat 31 OctMulhouse 13:110 min—
Fri 30 OctMulhouse 13:36+25 min+25 min
Thu 29 OctMulhouse 13:11No data—
Wed 28 OctMulhouse 13:110 min—
Tue 27 OctMulhouse 13:110 min—
Mon 26 OctMulhouse 13:11No data—
Sun 25 OctMulhouse 13:110 min—
Sat 24 OctMulhouse 13:110 min—
Fri 23 OctMulhouse 13:110 min—
Thu 22 OctMulhouse 13:11No data—
Wed 21 OctMulhouse 13:110 min—
Tue 20 OctMulhouse 13:110 min—
Mon 19 OctMulhouse 13:11No data—
Sun 18 OctMulhouse 13:110 min—