P42 861103 Vierzon → Montluçon

View line P42

Vierzon 10:21 → Montluçon 11:54 Mon, Tue, Wed, Thu, Fri, Sat 1 h 33 min · 6 stops SNCF

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 10:21 from Vierzon · Sat 21 Nov

Next departure 10:21 today · Vierzon
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
79%
30/38 runs under 3 min
RT coverage: 38 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 31 Aug Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8757629 +60 min
  • Mon 24 Aug Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8764135 +20 min
  • Sat 7 Nov Max en route +10 min · last fix heading to Montluçon +10 min
  • Thu 29 Oct Max en route +10 min · last fix heading to Montluçon +10 min
  • Wed 18 Nov Max en route +5 min · last fix heading to Montluçon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 30
  • 3–10 min 11% · 4
  • 10–30 min 8% · 3
  • 30+ min 3% · 1

On-time by weekday

  • 57% M n=7
  • 100% T n=7
  • 83% W n=6
  • 83% T n=6
  • 100% F n=6
  • 50% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 38 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
10:21on time +5 min
10:43 / 10:44≈ on time ≈ +6 min
10:55 / 10:58≈ on time ≈ +5 min
11:16 / 11:19≈ on time ≈ +5 min
11:37 / 11:38≈ on time ≈ +6 min
11:54on time +7 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
Fri 20 NovMontluçon 11:540 min—
Thu 19 NovMontluçon 11:540 min+10 min
Wed 18 NovMontluçon 11:59+5 min+5 min
Tue 17 NovMontluçon 11:540 min—
Mon 16 NovMontluçon 11:59+5 min+10 min
Sat 14 NovMontluçon 11:540 min—
Fri 13 NovMontluçon 11:540 min—
Thu 12 NovMontluçon 11:540 min—
Tue 10 NovMontluçon 11:540 min—
Mon 9 NovMontluçon 11:550 min—
Sat 7 NovMontluçon 12:04+10 min+10 min
Wed 4 NovMontluçon 11:540 min—
Tue 3 NovMontluçon 11:550 min+5 min
Mon 2 NovMontluçon 11:540 min—
Sat 31 OctMontluçon 11:560 min—
Fri 30 OctMontluçon 11:550 min—
Thu 29 OctMontluçon 12:46+10 min+10 min
Wed 28 OctMontluçon 12:360 min—
Tue 27 OctMontluçon 12:360 min—
Mon 26 OctMontluçon 12:360 min—
Sat 24 OctMontluçon 11:550 min—
Sat 17 OctMontluçon 12:00+5 min+5 min
Sat 10 OctMontluçon 12:00+5 min+5 min
Fri 11 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Thu 10 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Wed 9 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Tue 8 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Mon 7 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Fri 4 SeptStopPoint:OCETrain TER-8764100 11:530 min—
Thu 3 SeptStopPoint:OCETrain TER-8764100 11:530 min—