P132 861171 Bourges – Montluçon
Alerts for train 861171
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P132.
✓ Today’s run finished
Today it reached Montluçon at 15:58 0 min
- Bourges14:34
- Saint-Florent-sur-Cher14:46
- Châteauneuf-sur-Cher14:59
- Saint-Amand-Montrond - Orval15:22
- Vallon-en-Sully15:41
- Montluçon15:58
Next service: tomorrow 14:34 from Bourges · Tue 10 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 23 Oct Max en route +45 min · last fix heading to Montluçon +39 min
- Thu 24 Sept Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8764135 +30 min
- Sun 11 Oct Max en route +25 min · last fix heading to Montluçon +25 min
- Sat 24 Oct Max en route +15 min · last fix heading to Montluçon +15 min
- Sun 25 Oct Max en route +10 min · last fix heading to Montluçon +10 min
Distribution · 90 days
47 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 38
- 3–10 min 6% · 3
- 10–30 min 9% · 4
- 30+ min 4% · 2
On-time by weekday
- 100% M n=9
- 86% T n=7
- 88% W n=8
- 71% T n=7
- 60% F n=5
- 80% S n=5
- 67% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 47 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 |
|---|---|---|---|
| 14:34 | on time | +5 min | |
| 14:46 / 14:47 | ≈ on time | ≈ +7 min | |
| 14:59 / 15:03 | ≈ on time | ≈ +9 min | |
| 15:22 / 15:24 | ≈ on time | ≈ +11 min | |
| 15:41 / 15:42 | ≈ on time | ≈ +10 min | |
| 15:58 | on time | +10 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 |
|---|---|---|---|
| Mon 9 Nov | Montluçon 15:59 | 0 min | — |
| Sun 8 Nov | Montluçon 15:37 | 0 min | — |
| Sat 7 Nov | Montluçon 15:37 | 0 min | — |
| Fri 6 Nov | Montluçon 15:59 | 0 min | — |
| Wed 4 Nov | Montluçon 16:04 | +5 min | +5 min |
| Tue 3 Nov | Montluçon 16:00 | 0 min | — |
| Mon 2 Nov | Montluçon 15:59 | 0 min | — |
| Sun 1 Nov | Montluçon 15:37 | 0 min | — |
| Sat 31 Oct | Montluçon 15:38 | 0 min | +5 min |
| Fri 30 Oct | Montluçon 15:59 | 0 min | — |
| Thu 29 Oct | Montluçon 15:59 | 0 min | +5 min |
| Wed 28 Oct | Montluçon 15:59 | 0 min | — |
| Tue 27 Oct | Montluçon 16:13 | +5 min | +5 min |
| Mon 26 Oct | Montluçon 16:09 | 0 min | — |
| Sun 25 Oct | Montluçon 15:47 | +10 min | +10 min |
| Sat 24 Oct | Montluçon 15:52 | +15 min | +15 min |
| Fri 23 Oct | Montluçon 16:39 | +39 min | +45 min |
| Thu 22 Oct | Montluçon 15:59 | 0 min | — |
| Wed 21 Oct | Montluçon 15:59 | 0 min | +5 min |
| Tue 20 Oct | Montluçon 15:59 | 0 min | — |
| Mon 19 Oct | Montluçon 16:00 | 0 min | — |
| Sun 18 Oct | Montluçon 15:37 | 0 min | — |
| Sat 17 Oct | Montluçon 15:37 | 0 min | — |
| Fri 16 Oct | Montluçon 16:09 | +10 min | +20 min |
| Thu 15 Oct | Montluçon 15:59 | 0 min | +5 min |
| Wed 14 Oct | Montluçon 15:59 | 0 min | — |
| Tue 13 Oct | Montluçon 15:59 | 0 min | — |
| Mon 12 Oct | Montluçon 15:59 | 0 min | — |
| Sun 11 Oct | Montluçon 16:02 | +25 min | +25 min |
| Sat 10 Oct | Montluçon 15:38 | 0 min | — |