P132 861177 Bourges – Montluçon

View line P132

Bourges 21:18 → Montluçon 22:39 Daily 1 h 21 min · 6 stops SNCF

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:18 from Bourges · Sat 7 Nov

Next departure 21:18 today · Bourges
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 27 full · 1 partial · 0 no data
On-time · 90 days
93%
40/43 runs under 3 min
RT coverage: 42 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

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

  • Thu 24 Sept Max en route +55 min · last fix heading to StopPoint:OCETrain TER-8757629 +55 min
  • Sat 31 Oct Max en route +50 min · last fix heading to Montluçon +50 min
  • Thu 20 Aug Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8764100 +15 min

Distribution · 90 days

43 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 93% · 40
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 5% · 2

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=6
  • 80% T n=10
  • 100% F n=6
  • 80% S n=5
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 stops).

Last 90 days, 43 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.

StopSched.Usually 9 days in 10
21:18on time on time
21:30 / 21:31≈ on time ≈ +2 min
21:42 / 21:44≈ on time ≈ +3 min
22:03 / 22:05≈ on time ≈ +2 min
22:22 / 22:23≈ on time ≈ +1 min
22:39on 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

DateLast stopFinalMax
Fri 6 NovMontluçon 22:390 min—
Wed 4 NovMontluçon 22:390 min—
Tue 3 NovMontluçon 22:390 min—
Mon 2 NovMontluçon 22:390 min—
Sun 1 NovMontluçon 22:390 min—
Sat 31 OctMontluçon 23:31+50 min+50 min
Fri 30 OctMontluçon 22:400 min—
Thu 29 OctMontluçon 22:400 min—
Wed 28 OctMontluçon 22:400 min—
Tue 27 OctMontluçon 22:400 min—
Mon 26 OctMontluçon 22:410 min+5 min
Sun 25 OctMontluçon 22:400 min+5 min
Sat 24 OctMontluçon 22:410 min—
Fri 23 OctChâteauneuf-sur-Cher 21:35Partial coverage0 min—
Thu 22 OctMontluçon 22:400 min—
Wed 21 OctMontluçon 22:400 min—
Tue 20 OctMontluçon 22:400 min—
Mon 19 OctMontluçon 22:400 min—
Sun 18 OctMontluçon 22:400 min—
Sat 17 OctMontluçon 22:400 min—
Fri 16 OctMontluçon 22:400 min—
Thu 15 OctMontluçon 22:400 min—
Wed 14 OctMontluçon 22:400 min—
Tue 13 OctMontluçon 22:400 min—
Mon 12 OctMontluçon 22:400 min—
Sun 11 OctMontluçon 22:400 min—
Sat 10 OctMontluçon 22:400 min—
Fri 9 OctMontluçon 22:400 min—
Thu 8 OctMontluçon 22:400 min—
Wed 7 OctMontluçon 22:400 min—