P23 873014 Montluçon → Commentry
Alerts for train 873014
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P23.
TER 873014 Montluçon–Commentry: final delay under 3 min on 15 of its 17 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:29 (GMT+1).
An alert on this phone or computer when the 873014 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November 0 min
Next service: tomorrow 16:38 from Montluçon · Mon 23 Nov
Last 30 days
Arrival delay at Commentry, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 12 Nov Max en route +30 min · last fix heading to Commentry +30 min
- Wed 28 Oct Max en route +10 min · last fix heading to Commentry +10 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 34
- 3–10 min 0% · 0
- 10–30 min 3% · 1
- 30+ min 3% · 1
On-time by weekday
- 100% M n=8
- 100% T n=7
- 86% W n=7
- 86% T n=7
- 100% F n=7
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 16:38 | on time | on time | |
| 16:40 / 16:41 | ≈ on time | ≈ on time | |
| 16:51 | on time | on time |
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 20 Nov | Commentry 16:53 | 0 min | — |
| Thu 19 Nov | Commentry 16:52 | 0 min | — |
| Wed 18 Nov | Commentry 16:52 | 0 min | — |
| Mon 16 Nov | Commentry 16:53 | 0 min | — |
| Fri 13 Nov | Commentry 16:53 | 0 min | — |
| Thu 12 Nov | Commentry 17:22 | +30 min | +30 min |
| Tue 10 Nov | Commentry 16:53 | 0 min | — |
| Mon 9 Nov | Commentry 16:52 | 0 min | — |
| Fri 6 Nov | Commentry 16:52 | 0 min | — |
| Thu 5 Nov | Commentry 16:52 | No data | — |
| Wed 4 Nov | Commentry 16:52 | 0 min | — |
| Tue 3 Nov | Commentry 16:53 | 0 min | — |
| Mon 2 Nov | Commentry 16:52 | 0 min | — |
| Fri 30 Oct | Commentry 16:52 | 0 min | — |
| Thu 29 Oct | Commentry 16:52 | 0 min | — |
| Wed 28 Oct | Commentry 17:02 | +10 min | +10 min |
| Tue 27 Oct | Commentry 16:52 | 0 min | — |
| Mon 26 Oct | Commentry 16:53 | 0 min | — |
| Thu 22 Oct | Commentry 16:52 | 0 min | — |
| Wed 21 Oct | Commentry 16:53 | 0 min | — |
| Tue 20 Oct | Commentry 16:52 | 0 min | — |
| Mon 19 Oct | Commentry 16:53 | 0 min | — |
| Fri 16 Oct | Commentry 16:52 | 0 min | — |
| Thu 15 Oct | Commentry 16:52 | 0 min | — |
| Wed 14 Oct | Commentry 16:52 | 0 min | — |
| Tue 13 Oct | Commentry 16:52 | 0 min | — |
| Mon 12 Oct | Commentry 16:52 | 0 min | — |
| Fri 9 Oct | Commentry 16:52 | 0 min | — |
| Thu 8 Oct | Commentry 16:52 | 0 min | — |
| Wed 7 Oct | Commentry 16:52 | 0 min | — |