C12 96136 Basel SBB – Mulhouse

View line C12

Basel SBB 19:08 → Mulhouse 19:39 Mon, Tue, Wed, Thu, Fri, Sun 0 h 31 min · 9 stops SNCF

✓ Today’s run finished

Today it reached Mulhouse at 19:39 0 min

  1. Basel SBB19:08
  2. Bâle Saint-Jean19:13
  3. Saint-Louis la Chaussée19:19
  4. Bartenheim19:22
  5. Sierentz19:26
  6. Rixheim19:34
  7. Mulhouse19:39

Next service: tomorrow 19:08 from Basel SBB · Thu 12 Nov

Next departure 19:08 tomorrow · Basel SBB
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 1 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 25 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Mulhouse +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 75% W n=4
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • 83% S n=6

Stops and timetable

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

Last 90 days, 22 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
19:08on time on time
19:13≈ on time ≈ on time
19:16≈ on time ≈ on time
19:19≈ on time ≈ on time
19:22 / 19:23≈ on time ≈ on time
19:26≈ on time ≈ on time
19:32≈ on time ≈ on time
19:34 / 19:35≈ on time ≈ on time
19:39on time on time

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
Wed 11 NovMulhouse 19:390 min—
Tue 10 NovMulhouse 19:390 min—
Mon 9 NovRixheim 19:34Partial coverageNo data—
Sun 8 NovMulhouse 19:390 min—
Fri 6 NovMulhouse 19:400 min—
Wed 4 NovMulhouse 19:390 min—
Tue 3 NovMulhouse 19:390 min—
Mon 2 NovMulhouse 19:390 min—
Sun 1 NovMulhouse 19:390 min—
Sun 25 OctMulhouse 19:45+5 min+5 min
Sun 18 OctMulhouse 19:400 min—
Fri 16 OctMulhouse 19:400 min—
Thu 15 OctMulhouse 19:400 min—
Wed 14 OctMulhouse 19:400 min—
Tue 13 OctMulhouse 19:410 min—
Mon 12 OctMulhouse 19:400 min—
Sun 11 OctMulhouse 19:400 min—
Fri 9 OctMulhouse 19:400 min—
Thu 8 OctMulhouse 19:400 min—
Wed 7 OctMulhouse 19:45+5 min+5 min
Tue 6 OctMulhouse 19:400 min—
Mon 5 OctMulhouse 19:380 min—
Sun 4 OctStopPoint:OCETrain TE~cef89d1b 19:410 min—