P132 861174 Montluçon – Bourges

View line P132

Montluçon 19:06 → Bourges 20:27 Wed, Sun 1 h 21 min · 6 stops SNCF

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: Sunday 19:06 from Montluçon · Sun 8 Nov

Next departure 19:06 Sunday · Montluçon
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Bourges, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 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
  • 100% S n=13

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.

StopSched.Usually 9 days in 10
19:06on time on time
19:21 / 19:22≈ on time ≈ on time
19:39 / 19:40≈ on time ≈ on time
19:59 / 20:01≈ on time ≈ on time
20:13 / 20:14≈ on time ≈ on time
20:27on 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
Sun 1 NovBourges 20:280 min—
Sun 25 OctBourges 20:280 min—
Sun 18 OctBourges 20:280 min—
Sun 11 OctBourges 20:280 min—
Sun 4 OctStopPoint:OCETrain TE~7f733cac 20:290 min—
Wed 30 SeptStopPoint:OCETrain TER-8757620 20:26No data—
Sun 27 SeptStopPoint:OCETrain TER-8757620 20:260 min—
Wed 23 SeptStopPoint:OCETrain TER-8757620 20:26No data—
Sun 20 SeptStopPoint:OCETrain TER-8757620 20:270 min—
Wed 16 SeptStopPoint:OCETrain TER-8757620 20:26No data—
Sun 13 SeptStopPoint:OCETrain TER-8757620 20:260 min—
Wed 9 SeptStopPoint:OCETrain TER-8757620 20:26No data—
Sun 6 SeptStopPoint:OCETrain TER-8757620 20:260 min—
Wed 2 SeptStopPoint:OCETrain TER-8757620 20:27No data—
Sun 30 AugStopPoint:OCETrain TER-8757620 20:260 min—
Sun 23 AugStopPoint:OCETrain TER-8757620 20:260 min—
Wed 19 AugStopPoint:OCETrain TER-8757620 20:26No data—
Sun 16 AugStopPoint:OCETrain TER-8757620 20:260 min—
Wed 12 AugStopPoint:OCETrain TER-8757620 20:26No data—
Sun 9 AugStopPoint:OCETrain TER-8757620 20:260 min—