P22 873052 Clermont-Ferrand – Montluçon
Alerts for train 873052
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P22.
It does not run today
Last recorded run: Monday 16 November 0 min
Next service: Monday 06:35 from Clermont-Ferrand · Mon 23 Nov
Last 30 days
Arrival delay at Montluçon, 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 9 Nov Max en route +20 min · last fix heading to Montluçon +15 min
- Mon 31 Aug Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8764141 +15 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 82% · 9
- 3–10 min 0% · 0
- 10–30 min 18% · 2
- 30+ min 0% · 0
On-time by weekday
- 82% M n=11
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 11 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 |
|---|---|---|---|
| 06:35 | on time | on time | |
| 06:44 / 06:45 | ≈ on time | ≈ +1 min | |
| 06:55 / 06:56 | ≈ on time | ≈ +3 min | |
| 07:04 / 07:06 | ≈ on time | ≈ +4 min | |
| 07:14 / 07:15 | ≈ on time | ≈ +5 min | |
| 07:24 / 07:25 | ≈ on time | ≈ +7 min | |
| 07:33 / 07:39 | ≈ on time | ≈ +8 min | |
| 07:48 / 07:51 | ≈ on time | ≈ +10 min | |
| 08:06 / 08:14 | ≈ on time | ≈ +12 min | |
| 08:23 / 08:24 | ≈ on time | ≈ +14 min | |
| 08:27 | on time | +15 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 | Montluçon 08:28 | 0 min | — |
| Mon 9 Nov | Montluçon 08:43 | +15 min | +20 min |
| Mon 2 Nov | Montluçon 08:28 | 0 min | — |
| Mon 26 Oct | Montluçon 08:28 | 0 min | — |
| Mon 19 Oct | Montluçon 08:28 | 0 min | +5 min |
| Mon 12 Oct | Montluçon 08:28 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~b037709c 08:29 | 0 min | — |
| Mon 21 Sept | StopPoint:OCETrain TER-8773240 07:03 | 0 min | — |
| Mon 14 Sept | StopPoint:OCETrain TER-8773240 07:03 | 0 min | — |
| Mon 31 Aug | StopPoint:OCETrain TER-8764141 08:26 | +15 min | +25 min |
| Mon 24 Aug | StopPoint:OCETrain TER-8764100 08:26 | 0 min | — |