P23 873014 Montluçon → Commentry

View line P23

Montluçon 16:38 → Commentry 16:51 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 3 stops SNCF

TER 873014 Montluçon–Commentry: final delay under 3 min on 15 of its 17 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:29 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 16:38 from Montluçon · Mon 23 Nov

Next departure 16:38 tomorrow · Montluçon
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 36 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: +4 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

  • Thu 12 Nov Max en route +30 min · last fix heading to Commentry +30 min
  • Wed 28 Oct Max en route +10 min · last fix heading to Commentry +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 34
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 86% W n=7
  • 86% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
16:38on time on time
16:40 / 16:41≈ on time ≈ on time
16: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
Fri 20 NovCommentry 16:530 min—
Thu 19 NovCommentry 16:520 min—
Wed 18 NovCommentry 16:520 min—
Mon 16 NovCommentry 16:530 min—
Fri 13 NovCommentry 16:530 min—
Thu 12 NovCommentry 17:22+30 min+30 min
Tue 10 NovCommentry 16:530 min—
Mon 9 NovCommentry 16:520 min—
Fri 6 NovCommentry 16:520 min—
Thu 5 NovCommentry 16:52No data—
Wed 4 NovCommentry 16:520 min—
Tue 3 NovCommentry 16:530 min—
Mon 2 NovCommentry 16:520 min—
Fri 30 OctCommentry 16:520 min—
Thu 29 OctCommentry 16:520 min—
Wed 28 OctCommentry 17:02+10 min+10 min
Tue 27 OctCommentry 16:520 min—
Mon 26 OctCommentry 16:530 min—
Thu 22 OctCommentry 16:520 min—
Wed 21 OctCommentry 16:530 min—
Tue 20 OctCommentry 16:520 min—
Mon 19 OctCommentry 16:530 min—
Fri 16 OctCommentry 16:520 min—
Thu 15 OctCommentry 16:520 min—
Wed 14 OctCommentry 16:520 min—
Tue 13 OctCommentry 16:520 min—
Mon 12 OctCommentry 16:520 min—
Fri 9 OctCommentry 16:520 min—
Thu 8 OctCommentry 16:520 min—
Wed 7 OctCommentry 16:520 min—