P14 861552 Bourges – Vierzon
Alerts for train 861552
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P14.
Cancelled today · The operator has cancelled this train today. It is not running.
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: tomorrow 07:08 from Bourges · Fri 6 Nov
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 +40 min · last fix heading to Vierzon +40 min
- Tue 6 Oct Max en route +10 min · last fix heading to Vierzon +10 min
- Fri 16 Oct Max en route +5 min · last fix heading to Vierzon +5 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 77% · 10
- 3–10 min 8% · 1
- 10–30 min 8% · 1
- 30+ min 8% · 1
On-time by weekday
- 100% M n=3
- 33% T n=3
- 100% W n=3
- 100% T n=2
- 50% F n=2
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 07:08 | on time | on time | |
| 07:13 / 07:14 | ≈ on time | ≈ +2 min | |
| 07:19 / 07:20 | ≈ on time | ≈ +4 min | |
| 07:24 / 07:25 | ≈ on time | ≈ +5 min | |
| 07:29 / 07:30 | ≈ on time | ≈ +7 min | |
| 07:35 | on time | +9 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 |
|---|---|---|---|
| Wed 4 Nov | Vierzon 07:34 | 0 min | — |
| Tue 3 Nov | Vierzon 08:14 | +40 min | +40 min |
| Mon 2 Nov | Vierzon 07:34 | 0 min | — |
| Fri 16 Oct | Vierzon 07:42 | +5 min | +5 min |
| Thu 15 Oct | Vierzon 07:37 | 0 min | — |
| Wed 14 Oct | Vierzon 07:36 | 0 min | — |
| Tue 13 Oct | Vierzon 07:36 | 0 min | — |
| Mon 12 Oct | Vierzon 07:36 | 0 min | — |
| Fri 9 Oct | Vierzon 07:37 | 0 min | — |
| Thu 8 Oct | Vierzon 07:36 | 0 min | — |
| Wed 7 Oct | Vierzon 07:37 | 0 min | — |
| Tue 6 Oct | Vierzon 07:47 | +10 min | +10 min |
| Mon 5 Oct | StopPoint:OCETrain TE~de2ab70f 07:37 | 0 min | — |