C10 831421 Colmar – Mulhouse
Alerts for train 831421
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line C10.
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 16:04 from Colmar · Thu 5 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
- 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
Distribution · 90 days
23 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 21
- 3–10 min 9% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=5
- 100% W n=5
- 100% T n=4
- 75% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 23 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 |
|---|---|---|---|
| 16:04 | on time | on time | |
| 16:09 / 16:10 | ≈ on time | ≈ +1 min | |
| 16:14 | ≈ on time | ≈ +1 min | |
| 16:18 / 16:19 | ≈ on time | ≈ +2 min | |
| 16:22 | ≈ on time | ≈ +2 min | |
| 16:25 | ≈ on time | ≈ +2 min | |
| 16:28 / 16:29 | ≈ on time | ≈ +1 min | |
| 16:35 | ≈ on time | ≈ +1 min | |
| 16:40 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Mulhouse 16:39 | 0 min | — |
| Tue 3 Nov | Mulhouse 16:40 | 0 min | — |
| Mon 2 Nov | Mulhouse 16:39 | 0 min | — |
| Fri 30 Oct | Mulhouse 16:41 | 0 min | — |
| Thu 29 Oct | Mulhouse 16:41 | 0 min | +5 min |
| Wed 28 Oct | Mulhouse 16:41 | 0 min | — |
| Tue 27 Oct | Mulhouse 16:41 | 0 min | — |
| Mon 26 Oct | Mulhouse 16:42 | 0 min | — |
| Fri 23 Oct | Mulhouse 16:42 | 0 min | — |
| Thu 22 Oct | Mulhouse 16:42 | 0 min | — |
| Wed 21 Oct | Mulhouse 16:41 | 0 min | — |
| Tue 20 Oct | Mulhouse 16:41 | 0 min | — |
| Mon 19 Oct | Mulhouse 16:42 | 0 min | — |
| Fri 16 Oct | Mulhouse 16:41 | 0 min | — |
| Thu 15 Oct | Mulhouse 16:41 | 0 min | — |
| Wed 14 Oct | Mulhouse 16:41 | 0 min | — |
| Tue 13 Oct | Mulhouse 16:41 | 0 min | — |
| Mon 12 Oct | Mulhouse 16:46 | +5 min | +5 min |
| Fri 9 Oct | Mulhouse 16:46 | +5 min | +5 min |
| Thu 8 Oct | Mulhouse 16:41 | 0 min | — |
| Wed 7 Oct | Mulhouse 16:41 | 0 min | — |
| Tue 6 Oct | Mulhouse 16:41 | 0 min | — |
| Mon 5 Oct | Mulhouse 16:42 | 0 min | — |