P42 861124 Montluçon – Vierzon

View line P42

Montluçon 06:11 → Vierzon 07:40 Sat 1 h 29 min · 6 stops SNCF

It does not run today

Last recorded run: Saturday 14 November 0 min

Next service: Saturday 06:11 from Montluçon · Sat 21 Nov

Next departure 06:11 Saturday · Montluçon
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Sat 17 Oct Max en route +10 min · last fix heading to Vierzon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 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
  • 83% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 6 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
06:11on time +3 min
06:25 / 06:26≈ on time ≈ +3 min
06:44 / 06:45≈ on time ≈ +3 min
07:03 / 07:04≈ on time ≈ +3 min
07:15 / 07:16≈ on time ≈ +3 min
07:40on time +3 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
Sat 14 NovVierzon 07:390 min—
Sat 7 NovVierzon 07:390 min—
Sat 31 OctVierzon 07:410 min—
Sat 24 OctVierzon 07:410 min—
Sat 17 OctVierzon 07:46+5 min+10 min
Sat 10 OctVierzon 07:410 min—