P32 861139 Bourges – Montluçon
Alerts for train 861139
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P32.
It does not run today
Last recorded run: Sunday 8 November 0 min
Next service: Wednesday 19:30 from Bourges · Wed 11 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
- Sun 30 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8764137 +10 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 9
- 3–10 min 0% · 0
- 10–30 min 10% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 90% S n=10
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 19:30 | on time | on time | |
| 19:43 / 19:44 | ≈ on time | ≈ on time | |
| 19:49 / 19:50 | ≈ on time | ≈ on time | |
| 19:58 / 20:03 | ≈ on time | ≈ on time | |
| 20:09 / 20:10 | ≈ on time | ≈ on time | |
| 20:24 / 20:25 | ≈ on time | ≈ +1 min | |
| 20:36 / 20:37 | ≈ on time | ≈ +1 min | |
| 20:44 / 20:45 | ≈ on time | ≈ +1 min | |
| 20:51 / 20:52 | ≈ on time | ≈ +1 min | |
| 20:57 / 20:58 | ≈ on time | ≈ +1 min | |
| 21:03 / 21:04 | ≈ on time | ≈ +1 min | |
| 21:07 | on time | +1 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 |
|---|---|---|---|
| Sun 8 Nov | Montluçon 21:08 | 0 min | — |
| Sun 1 Nov | Montluçon 21:08 | 0 min | — |
| Sun 25 Oct | Montluçon 21:08 | 0 min | — |
| Sun 18 Oct | Montluçon 21:08 | 0 min | — |
| Sun 11 Oct | Montluçon 21:08 | 0 min | — |
| Sun 4 Oct | StopPoint:OCETrain TE~b037709c 21:09 | 0 min | — |
| Sun 27 Sept | StopPoint:OCETrain TER-8764100 21:06 | 0 min | — |
| Wed 2 Sept | StopPoint:OCETrain TER-8764100 21:07 | No data | — |
| Sun 30 Aug | StopPoint:OCETrain TER-8764137 21:06 | +10 min | +10 min |
| Sun 23 Aug | StopPoint:OCETrain TER-8764100 21:06 | 0 min | — |
| Wed 19 Aug | StopPoint:OCETrain TER-8764100 21:06 | No data | — |
| Sun 16 Aug | StopPoint:OCETrain TER-8764100 21:06 | 0 min | — |
| Wed 12 Aug | StopPoint:OCETrain TER-8764100 21:06 | No data | — |