P23 873003 Commentry – Montluçon

View line P23

Commentry 07:37 → Montluçon 07:51 Mon, Tue, Thu, Fri, Sat 0 h 14 min · 3 stops SNCF

✓ Today’s run finished

Today it reached Montluçon at 07:51 0 min

  1. Commentry07:37
  2. Montluçon Rimard07:46
  3. Montluçon07:51

Next service: tomorrow 07:37 from Commentry · Tue 10 Nov

Next departure 07:37 tomorrow · Commentry
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 1 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 1 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Montluçon +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 88% F n=8
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
07:37on time on time
07:46 / 07:47≈ on time ≈ on time
07:51on 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
Mon 9 NovMontluçon 07:520 min—
Sat 7 NovMontluçon 07:520 min—
Fri 6 NovMontluçon 07:520 min—
Thu 5 NovMontluçon 07:52No data—
Wed 4 NovMontluçon 07:520 min—
Tue 3 NovMontluçon 07:520 min—
Sat 31 OctMontluçon 07:520 min—
Fri 30 OctMontluçon 07:520 min—
Thu 29 OctMontluçon 07:520 min—
Wed 28 OctMontluçon 07:520 min—
Tue 27 OctMontluçon 07:520 min—
Mon 26 OctMontluçon 07:520 min—
Sat 24 OctMontluçon 07:520 min—
Fri 23 OctMontluçon 07:520 min—
Thu 22 OctMontluçon 07:520 min—
Wed 21 OctMontluçon 07:520 min—
Tue 20 OctMontluçon 07:520 min—
Sat 17 OctMontluçon 07:520 min—
Fri 16 OctMontluçon 07:530 min—
Thu 15 OctMontluçon 07:520 min—
Wed 14 OctMontluçon 07:520 min—
Tue 13 OctMontluçon 07:520 min—
Mon 12 OctMontluçon 07:520 min—
Sat 10 OctMontluçon 07:520 min—
Fri 9 OctMontluçon 07:58+5 min+5 min
Thu 8 OctMontluçon 07:520 min—
Wed 7 OctMontluçon 07:530 min—
Tue 6 OctMontluçon 07:530 min—
Mon 5 OctStopPoint:OCETrain TE~b037709c 07:530 min—
Fri 28 AugStopPoint:OCETrain TER-8764100 07:500 min—