C10 831419 Colmar – Mulhouse
Alerts for train 831419
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.
✓ Today’s run finished
Today it reached Mulhouse at 14:40 0 min
- Colmar14:12
- Rouffach14:19
- Bollwiller14:27
- Mulhouse Dornach14:35
- Mulhouse14:40
Next service: tomorrow 14:12 from Colmar · Tue 17 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 1 Sept Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8718270 +15 min
- Tue 3 Nov Max en route +10 min · last fix heading to Mulhouse +10 min
- Wed 14 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
- Mon 28 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8718205 +5 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 22
- 3–10 min 8% · 2
- 10–30 min 8% · 2
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 67% T n=6
- 75% W n=4
- 100% T n=5
- 100% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 26 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 |
|---|---|---|---|
| 14:12 | on time | on time | |
| 14:19 / 14:20 | ≈ on time | ≈ +3 min | |
| 14:27 | ≈ on time | ≈ +3 min | |
| 14:35 | ≈ on time | ≈ +4 min | |
| 14:40 | 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 |
|---|---|---|---|
| Mon 16 Nov | Mulhouse 14:39 | 0 min | — |
| Fri 13 Nov | Mulhouse 14:39 | 0 min | — |
| Thu 12 Nov | Mulhouse 14:39 | 0 min | — |
| Wed 11 Nov | Mulhouse 14:39 | No data | — |
| Tue 10 Nov | Mulhouse 14:39 | 0 min | — |
| Mon 9 Nov | Mulhouse 14:39 | 0 min | — |
| Fri 6 Nov | Mulhouse 14:39 | 0 min | — |
| Thu 5 Nov | Mulhouse 14:39 | 0 min | — |
| Wed 4 Nov | Mulhouse 14:39 | 0 min | — |
| Tue 3 Nov | Mulhouse 14:50 | +10 min | +10 min |
| Mon 2 Nov | Mulhouse 14:39 | 0 min | +5 min |
| Fri 16 Oct | Mulhouse 14:41 | 0 min | — |
| Thu 15 Oct | Mulhouse 14:41 | 0 min | — |
| Wed 14 Oct | Mulhouse 14:46 | +5 min | +5 min |
| Tue 13 Oct | Mulhouse 14:41 | 0 min | — |
| Mon 12 Oct | Mulhouse 14:41 | 0 min | — |
| Fri 9 Oct | Mulhouse 14:41 | 0 min | — |
| Thu 8 Oct | Mulhouse 14:41 | 0 min | — |
| Wed 7 Oct | Mulhouse 14:41 | 0 min | — |
| Tue 6 Oct | Mulhouse 14:41 | 0 min | — |
| Mon 5 Oct | Mulhouse 14:41 | 0 min | — |
| Mon 28 Sept | StopPoint:OCETrain TER-8718205 14:40 | +5 min | +10 min |
| Fri 25 Sept | StopPoint:OCETrain TER-8718206 14:39 | 0 min | +5 min |
| Thu 10 Sept | StopPoint:OCETrain TER-8718206 14:39 | 0 min | +10 min |
| Wed 2 Sept | StopPoint:OCETrain TER-8718206 14:40 | 0 min | +10 min |
| Tue 1 Sept | StopPoint:OCETrain TER-8718270 14:39 | +15 min | +15 min |
| Tue 25 Aug | StopPoint:OCETrain TER-8718206 14:40 | 0 min | +5 min |