P132 861170 Montluçon – Bourges

View line P132

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

✓ Today’s run finished

Today it reached Bourges at 09:39 0 min

  1. Montluçon08:18
  2. Vallon-en-Sully08:33
  3. Saint-Amand-Montrond - Orval08:51
  4. Châteauneuf-sur-Cher09:12
  5. Saint-Florent-sur-Cher09:25
  6. Bourges09:39

Next service: tomorrow 08:18 from Montluçon · Wed 11 Nov

Next departure 08:18 tomorrow · Montluçon
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
86%
32/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

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

Worst days

  • Sun 25 Oct Max en route +55 min · last fix heading to Bourges +50 min
  • Wed 14 Oct Max en route +45 min · last fix heading to Bourges +45 min
  • Fri 9 Oct Max en route +30 min · last fix heading to Bourges +30 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Bourges +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Bourges +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 32
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 8% · 3

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
08:18on time on time
08:33 / 08:34≈ on time ≈ +1 min
08:51 / 08:53≈ on time ≈ +2 min
09:12 / 09:14≈ on time ≈ +3 min
09:25 / 09:26≈ on time ≈ +4 min
09:39on time +5 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

DateLast stopFinalMax
Tue 10 NovBourges 09:390 min—
Mon 9 NovBourges 09:390 min—
Sun 8 NovBourges 09:390 min—
Sat 7 NovBourges 09:390 min—
Fri 6 NovBourges 09:390 min—
Wed 4 NovBourges 09:390 min—
Tue 3 NovBourges 09:400 min—
Mon 2 NovBourges 09:44+5 min+5 min
Sun 1 NovBourges 09:410 min—
Sat 31 OctBourges 09:400 min—
Fri 30 OctBourges 09:400 min—
Thu 29 OctBourges 09:400 min—
Wed 28 OctBourges 09:400 min—
Tue 27 OctBourges 09:400 min—
Mon 26 OctBourges 09:400 min—
Sun 25 OctBourges 10:30+50 min+55 min
Sat 24 OctBourges 09:400 min—
Fri 23 OctBourges 09:400 min—
Thu 22 OctBourges 09:400 min—
Wed 21 OctBourges 09:400 min—
Tue 20 OctBourges 09:45+5 min+5 min
Mon 19 OctBourges 09:410 min—
Sun 18 OctBourges 09:400 min—
Sat 17 OctBourges 09:400 min—
Fri 16 OctBourges 09:400 min—
Thu 15 OctBourges 09:400 min—
Wed 14 OctBourges 10:25+45 min+45 min
Tue 13 OctBourges 09:400 min—
Mon 12 OctBourges 09:410 min—
Sun 11 OctBourges 09:400 min—