P42 861102 Montluçon – Vierzon
Alerts for train 861102
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P42.
Running now · updated 06:46
Between Saint-Florent-sur-Cher and Vierzon 0 min
Estimated arrival at Vierzon 07:03 · 95 km/h
- Montluçon05:34
- Vallon-en-Sully05:48
- Saint-Amand-Montrond - Orval06:07
- Châteauneuf-sur-Cher06:26
- Saint-Florent-sur-Cher06:38
- Vierzon07:03
Today it is running no worse than usual: typical arrival delay is 0 min; 77% of the last 22 runs arrived on time.
Last 30 days
Arrival delay at Vierzon, 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 3 Nov Max en route +5 min · last fix heading to Vierzon +5 min
- Mon 26 Oct Max en route +5 min · last fix heading to Vierzon +5 min
- Thu 22 Oct Max en route +5 min · last fix heading to Vierzon +5 min
- Sat 10 Oct Max en route +5 min · last fix heading to Vierzon +5 min
- Fri 9 Oct Max en route +10 min · last fix heading to Vierzon +5 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 75% · 21
- 3–10 min 25% · 7
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=6
- 80% T n=5
- 100% W n=5
- 50% T n=4
- 75% F n=4
- 75% S n=4
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 28 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 | Today |
|---|---|---|---|---|
| 05:34 | on time | on time | Passed | |
| 05:48 / 05:49 | ≈ on time | ≈ +1 min | Passed | |
| 06:07 / 06:08 | ≈ on time | ≈ +2 min | Passed | |
| 06:26 / 06:27 | ≈ on time | ≈ +3 min | Passed | |
| 06:38 / 06:39 | ≈ on time | ≈ +4 min | Passed | |
| 07:03 | 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 |
|---|---|---|---|
| Sat 7 Nov | Vierzon 06:44 | 0 min | — |
| Thu 5 Nov | Vierzon 07:04 | No data | — |
| Wed 4 Nov | Vierzon 07:04 | 0 min | — |
| Tue 3 Nov | Vierzon 07:09 | +5 min | +5 min |
| Mon 2 Nov | Vierzon 07:04 | 0 min | — |
| Sat 31 Oct | Vierzon 07:04 | 0 min | — |
| Fri 30 Oct | Vierzon 07:04 | 0 min | — |
| Thu 29 Oct | Vierzon 07:04 | 0 min | — |
| Wed 28 Oct | Vierzon 07:04 | 0 min | — |
| Tue 27 Oct | Vierzon 07:04 | 0 min | — |
| Mon 26 Oct | Vierzon 07:09 | +5 min | +5 min |
| Fri 23 Oct | Vierzon 07:04 | 0 min | — |
| Thu 22 Oct | Vierzon 07:09 | +5 min | +5 min |
| Wed 21 Oct | Vierzon 07:04 | 0 min | — |
| Mon 19 Oct | Vierzon 07:04 | 0 min | — |
| Sat 17 Oct | Vierzon 07:04 | 0 min | — |
| Fri 16 Oct | Vierzon 07:05 | 0 min | — |
| Thu 15 Oct | Vierzon 07:04 | 0 min | — |
| Wed 14 Oct | Vierzon 07:04 | 0 min | — |
| Tue 13 Oct | Vierzon 07:04 | 0 min | — |
| Mon 12 Oct | Vierzon 07:04 | 0 min | — |
| Sat 10 Oct | Vierzon 07:09 | +5 min | +5 min |
| Fri 9 Oct | Vierzon 07:10 | +5 min | +10 min |
| Thu 8 Oct | Vierzon 07:09 | +5 min | +5 min |
| Wed 7 Oct | Vierzon 07:04 | 0 min | — |
| Tue 6 Oct | Vierzon 07:05 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~de2ab70f 07:10 | +5 min | +5 min |
| Tue 8 Sept | StopPoint:OCETrain TER-8757600 07:02 | 0 min | — |
| Mon 10 Aug | StopPoint:OCETrain TER-8757600 07:02 | 0 min | — |