P23 873008 Montluçon – Commentry

View line P23

Montluçon 08:04 → Commentry 08:17 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 3 stops SNCF

✓ Today’s run finished

Today it reached Commentry at 08:17 0 min

  1. Montluçon08:04
  2. Montluçon Rimard08:06
  3. Commentry08:17

Next service: Monday 08:04 from Montluçon · Mon 9 Nov

Next departure 08:04 Monday · Montluçon
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 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 Commentry, in minutes. One bar per run.

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

Worst days

  • Tue 27 Oct Max en route +5 min · last fix heading to Commentry +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:04on time on time
08:06 / 08:07≈ on time ≈ on time
08:17on 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
Fri 6 NovCommentry 08:180 min—
Thu 5 NovCommentry 08:18No data—
Wed 4 NovCommentry 08:180 min—
Tue 3 NovCommentry 08:180 min—
Mon 2 NovCommentry 08:180 min—
Fri 30 OctCommentry 08:180 min—
Thu 29 OctCommentry 08:180 min—
Wed 28 OctCommentry 08:180 min—
Tue 27 OctCommentry 08:23+5 min+5 min
Mon 26 OctCommentry 08:180 min—
Fri 23 OctCommentry 08:180 min—
Thu 22 OctCommentry 08:180 min—
Wed 21 OctCommentry 08:180 min—
Tue 20 OctCommentry 08:180 min—
Mon 19 OctCommentry 08:180 min—
Fri 16 OctCommentry 08:180 min—
Thu 15 OctCommentry 08:180 min—
Wed 14 OctCommentry 08:180 min—
Tue 13 OctCommentry 08:180 min—
Mon 12 OctCommentry 08:180 min—
Fri 9 OctCommentry 08:190 min—
Thu 8 OctCommentry 08:180 min—
Wed 7 OctCommentry 08:190 min—
Tue 6 OctCommentry 08:180 min—
Mon 5 OctStopPoint:OCETrain TE~91a57fb2 08:190 min—
Thu 13 AugStopPoint:OCETrain TER-8764141 08:160 min—
Wed 12 AugStopPoint:OCETrain TER-8764141 08:160 min—
Tue 11 AugStopPoint:OCETrain TER-8764141 08:160 min—
Mon 10 AugStopPoint:OCETrain TER-8764141 08:160 min—