K200 96242 Basel SBB – Mulhouse
Alerts for train 96242
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line K200.
It does not run today
Last recorded run: Wednesday 11 November 0 min
Next service: tomorrow 20:21 from Basel SBB · Sun 15 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
- Sun 4 Oct Max en route +50 min · last fix heading to StopPoint:OCETrain TE~cef89d1b +50 min
- Sun 25 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
- Sun 13 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8718206 +5 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 77% · 10
- 3–10 min 15% · 2
- 10–30 min 0% · 0
- 30+ min 8% · 1
On-time by weekday
- — M n=0
- — T n=0
- 100% W n=1
- — T n=0
- — F n=0
- — S n=0
- 75% S n=12
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 20:21 | on time | on time | |
| 20:29 / 20:30 | ≈ on time | ≈ +2 min | |
| 20:44 | 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 |
|---|---|---|---|
| Wed 11 Nov | Mulhouse 20:44 | 0 min | — |
| Sun 8 Nov | Mulhouse 20:44 | 0 min | — |
| Sun 1 Nov | Mulhouse 20:44 | 0 min | — |
| Sun 25 Oct | Mulhouse 20:50 | +5 min | +5 min |
| Sun 18 Oct | Mulhouse 20:45 | 0 min | — |
| Sun 11 Oct | Mulhouse 20:45 | 0 min | — |
| Sun 4 Oct | StopPoint:OCETrain TE~cef89d1b 21:36 | +50 min | +50 min |
| Wed 30 Sept | StopPoint:OCETrain TER-8718206 20:43 | No data | — |
| Sun 27 Sept | StopPoint:OCETrain TER-8718206 20:43 | 0 min | — |
| Wed 23 Sept | StopPoint:OCETrain TER-8718206 20:43 | No data | — |
| Sun 20 Sept | StopPoint:OCETrain TER-8718206 20:44 | 0 min | — |
| Wed 16 Sept | StopPoint:OCETrain TER-8718206 20:43 | No data | — |
| Sun 13 Sept | StopPoint:OCETrain TER-8718206 20:43 | +5 min | +5 min |
| Wed 9 Sept | StopPoint:OCETrain TER-8718206 20:43 | No data | — |
| Sun 6 Sept | StopPoint:OCETrain TER-8718206 20:43 | 0 min | — |
| Wed 2 Sept | StopPoint:OCETrain TER-8718206 20:44 | No data | — |
| Sun 30 Aug | StopPoint:OCETrain TER-8718206 20:43 | 0 min | — |
| Wed 26 Aug | StopPoint:OCETrain TER-8718206 20:43 | No data | — |
| Sun 23 Aug | StopPoint:OCETrain TER-8718206 20:43 | 0 min | — |
| Wed 19 Aug | StopPoint:OCETrain TER-8718206 20:43 | No data | — |