C10 873303 Clermont-Ferrand – Vertaizon
Alerts for train 873303
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: tomorrow 08:28 from Clermont-Ferrand · Mon 16 Nov
Last 30 days
Arrival delay at Vertaizon, 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 +20 min · last fix heading to Vertaizon +20 min
- Thu 12 Nov Max en route +10 min · last fix heading to Vertaizon +10 min
- Fri 13 Nov Max en route +5 min · last fix heading to Vertaizon +5 min
- Thu 22 Oct Max en route +5 min · last fix heading to Vertaizon +5 min
- Mon 12 Oct Max en route +5 min · last fix heading to Vertaizon +5 min
Distribution · 90 days
42 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 35
- 3–10 min 12% · 5
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 67% M n=12
- 100% T n=8
- 100% W n=7
- 71% T n=7
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 42 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:28 | on time | on time | |
| 08:35 / 08:37 | ≈ on time | ≈ +3 min | |
| 08:42 / 08:43 | ≈ on time | ≈ +4 min | |
| 08:47 | 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 | Vertaizon 08:53 | +5 min | +5 min |
| Thu 12 Nov | Vertaizon 08:59 | +10 min | +10 min |
| Tue 10 Nov | Vertaizon 08:48 | 0 min | — |
| Mon 9 Nov | Vertaizon 08:48 | 0 min | +5 min |
| Fri 6 Nov | Vertaizon 08:48 | 0 min | — |
| Thu 5 Nov | Vertaizon 08:48 | No data | — |
| Wed 4 Nov | Vertaizon 08:48 | 0 min | — |
| Tue 3 Nov | Vertaizon 08:49 | 0 min | — |
| Mon 2 Nov | Vertaizon 09:08 | +20 min | +20 min |
| Fri 30 Oct | Vertaizon 08:48 | 0 min | — |
| Thu 29 Oct | Vertaizon 08:48 | 0 min | — |
| Wed 28 Oct | Vertaizon 08:48 | 0 min | — |
| Tue 27 Oct | Vertaizon 08:48 | 0 min | — |
| Mon 26 Oct | Vertaizon 08:48 | 0 min | — |
| Fri 23 Oct | Vertaizon 08:48 | 0 min | — |
| Thu 22 Oct | Vertaizon 08:53 | +5 min | +5 min |
| Wed 21 Oct | Vertaizon 08:48 | 0 min | — |
| Tue 20 Oct | Vertaizon 08:48 | 0 min | — |
| Mon 19 Oct | Vertaizon 08:48 | 0 min | — |
| Fri 16 Oct | Vertaizon 08:48 | 0 min | — |
| Thu 15 Oct | Vertaizon 08:48 | 0 min | — |
| Wed 14 Oct | Vertaizon 08:48 | 0 min | — |
| Tue 13 Oct | Vertaizon 08:48 | 0 min | — |
| Mon 12 Oct | Vertaizon 08:54 | +5 min | +5 min |
| Fri 9 Oct | Vertaizon 08:48 | 0 min | — |
| Thu 8 Oct | Vertaizon 08:48 | 0 min | — |
| Wed 7 Oct | Vertaizon 08:49 | 0 min | — |
| Tue 6 Oct | Vertaizon 08:48 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~a8178e16 08:54 | +5 min | +5 min |
| Mon 28 Sept | StopPoint:OCETrain TER-8773442 08:46 | 0 min | — |