C12 96146 Basel SBB – Mulhouse
Alerts for train 96146
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line C12.
✓ Today’s run finished
Today it reached Mulhouse at 09:39 0 min
- Basel SBB09:08
- Bâle Saint-Jean09:13
- Saint-Louis la Chaussée09:19
- Bartenheim09:22
- Sierentz09:26
- Rixheim09:34
- Mulhouse09:39
Next service: Monday 09:08 from Basel SBB · Mon 9 Nov
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
- Tue 3 Nov Max en route +5 min · last fix heading to Mulhouse +5 min
- Mon 12 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
- Fri 9 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
- Tue 6 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 73% · 11
- 3–10 min 27% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 33% T n=3
- 100% W n=3
- 100% T n=3
- 67% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 15 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 09:08 | on time | on time | |
| 09:13 | ≈ on time | ≈ +1 min | |
| 09:16 | ≈ on time | ≈ +1 min | |
| 09:19 | ≈ on time | ≈ +2 min | |
| 09:22 / 09:23 | ≈ on time | ≈ +2 min | |
| 09:26 | ≈ on time | ≈ +3 min | |
| 09:32 | ≈ on time | ≈ +4 min | |
| 09:34 / 09:35 | ≈ on time | ≈ +4 min | |
| 09:39 | on time | +5 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Mulhouse 09:39 | 0 min | — |
| Thu 5 Nov | Mulhouse 09:39 | 0 min | — |
| Wed 4 Nov | Mulhouse 09:39 | 0 min | — |
| Tue 3 Nov | Mulhouse 09:44 | +5 min | +5 min |
| Mon 2 Nov | Mulhouse 09:39 | 0 min | — |
| Fri 16 Oct | Mulhouse 09:40 | 0 min | — |
| Thu 15 Oct | Mulhouse 09:40 | 0 min | — |
| Wed 14 Oct | Mulhouse 09:40 | 0 min | — |
| Tue 13 Oct | Mulhouse 09:40 | 0 min | — |
| Mon 12 Oct | Mulhouse 09:46 | +5 min | +5 min |
| Fri 9 Oct | Mulhouse 09:46 | +5 min | +5 min |
| Thu 8 Oct | Mulhouse 09:40 | 0 min | — |
| Wed 7 Oct | Mulhouse 09:41 | 0 min | — |
| Tue 6 Oct | Mulhouse 09:45 | +5 min | +5 min |
| Mon 5 Oct | StopPoint:OCETrain TE~cef89d1b 09:41 | 0 min | — |