C10 831408 Mulhouse – Colmar
Alerts for train 831408
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 does not run today
Last recorded run: Friday 13 November +5 min
Next service: Monday 08:20 from Mulhouse · Mon 16 Nov
Last 30 days
Arrival delay at Colmar, 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 2 Nov Max en route +10 min · last fix heading to Colmar +10 min
- Fri 13 Nov Max en route +5 min · last fix heading to Colmar +5 min
- Mon 9 Nov Max en route +10 min · last fix heading to Colmar +5 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 84% · 16
- 3–10 min 11% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 50% M n=4
- 100% T n=4
- 100% W n=3
- 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, 19 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 |
|---|---|---|---|
| 08:20 | on time | +1 min | |
| 08:23 / 08:24 | ≈ on time | ≈ +1 min | |
| 08:31 | ≈ on time | ≈ +2 min | |
| 08:34 / 08:35 | ≈ on time | ≈ +2 min | |
| 08:38 / 08:39 | ≈ on time | ≈ +2 min | |
| 08:42 | ≈ on time | ≈ +3 min | |
| 08:47 | ≈ on time | ≈ +4 min | |
| 08:52 | ≈ on time | ≈ +4 min | |
| 08:58 | 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 13 Nov | Colmar 09:04 | +5 min | +5 min |
| Thu 12 Nov | Colmar 09:00 | 0 min | — |
| Wed 11 Nov | Colmar 08:59 | No data | — |
| Tue 10 Nov | Colmar 08:59 | 0 min | — |
| Mon 9 Nov | Colmar 09:04 | +5 min | +10 min |
| Fri 6 Nov | Colmar 08:59 | 0 min | — |
| Thu 5 Nov | Colmar 08:59 | 0 min | — |
| Wed 4 Nov | Colmar 08:59 | 0 min | — |
| Tue 3 Nov | Colmar 08:59 | 0 min | — |
| Mon 2 Nov | Colmar 09:09 | +10 min | +10 min |
| Fri 16 Oct | Colmar 08:59 | 0 min | — |
| Thu 15 Oct | Colmar 08:59 | 0 min | — |
| Wed 14 Oct | Colmar 08:59 | 0 min | — |
| Tue 13 Oct | Colmar 08:59 | 0 min | — |
| Mon 12 Oct | Colmar 09:00 | 0 min | — |
| Fri 9 Oct | Colmar 09:00 | 0 min | — |
| Thu 8 Oct | Colmar 08:59 | 0 min | — |
| Wed 7 Oct | Colmar 09:00 | 0 min | — |
| Tue 6 Oct | Colmar 08:59 | 0 min | +5 min |
| Mon 5 Oct | StopPoint:OCETrain TE~3fd1c682 09:00 | 0 min | — |