P22 873050 Clermont-Ferrand – Montluçon
Alerts for train 873050
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.
✓ Today’s run finished
Today, last fix heading to Montluçon at 07:33 No data
- Clermont-Ferrand06:00
- Riom - Châtel-Guyon06:08
- Bellenaves06:43
- Louroux-de-Bouble06:53
- Lapeyrouse07:02
- Montluçon Rimard07:28
- Montluçon07:32
Next service: tomorrow 06:00 from Clermont-Ferrand · Fri 6 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
- Fri 9 Oct Max en route +10 min · last fix heading to Montluçon +10 min
- Wed 28 Oct Max en route +10 min · last fix heading to Montluçon +5 min
- Tue 27 Oct Max en route +5 min · last fix heading to Montluçon +5 min
- Mon 5 Oct Max en route +5 min · last fix heading to StopPoint:OCETrain TE~b037709c +5 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 23
- 3–10 min 11% · 3
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 89% M n=9
- 80% T n=5
- 80% 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, 27 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:00 | on time | on time | |
| 06:08 / 06:09 | ≈ on time | ≈ on time | |
| 06:25 / 06:26 | ≈ on time | ≈ +1 min | |
| 06:43 / 06:46 | ≈ on time | ≈ +2 min | |
| 06:53 / 06:54 | ≈ on time | ≈ +3 min | |
| 07:02 / 07:03 | ≈ on time | ≈ +3 min | |
| 07:18 / 07:19 | ≈ on time | ≈ +4 min | |
| 07:28 / 07:29 | ≈ on time | ≈ +5 min | |
| 07:32 | 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 |
|---|---|---|---|
| Thu 5 Nov | Montluçon 07:33 | No data | — |
| Wed 4 Nov | Montluçon 07:33 | 0 min | — |
| Tue 3 Nov | Montluçon 07:33 | 0 min | — |
| Mon 2 Nov | Montluçon 07:33 | 0 min | — |
| Fri 30 Oct | Montluçon 07:33 | 0 min | — |
| Thu 29 Oct | Montluçon 07:33 | 0 min | — |
| Wed 28 Oct | Montluçon 07:38 | +5 min | +10 min |
| Tue 27 Oct | Montluçon 07:38 | +5 min | +5 min |
| Mon 26 Oct | Montluçon 07:33 | 0 min | — |
| Fri 23 Oct | Montluçon 07:33 | 0 min | — |
| Thu 22 Oct | Montluçon 07:33 | 0 min | — |
| Wed 21 Oct | Montluçon 07:33 | 0 min | — |
| Tue 20 Oct | Montluçon 07:33 | 0 min | — |
| Mon 19 Oct | Montluçon 07:33 | 0 min | — |
| Fri 16 Oct | Montluçon 07:34 | 0 min | — |
| Thu 15 Oct | Montluçon 07:34 | 0 min | — |
| Wed 14 Oct | Montluçon 07:33 | 0 min | — |
| Tue 13 Oct | Montluçon 07:33 | 0 min | — |
| Mon 12 Oct | Montluçon 07:33 | 0 min | — |
| Fri 9 Oct | Montluçon 07:44 | +10 min | +10 min |
| Thu 8 Oct | Montluçon 07:33 | 0 min | — |
| Wed 7 Oct | Montluçon 07:34 | 0 min | — |
| Tue 6 Oct | Montluçon 07:34 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~b037709c 07:39 | +5 min | +5 min |
| Mon 21 Sept | StopPoint:OCETrain TER-8773240 06:24 | 0 min | — |
| Mon 14 Sept | StopPoint:OCETrain TER-8773240 06:24 | 0 min | — |
| Mon 17 Aug | StopPoint:OCETrain TER-8764100 07:31 | 0 min | — |
| Mon 10 Aug | StopPoint:OCETrain TER-8764100 07:31 | 0 min | — |