C10 873316 Vertaizon – Clermont-Ferrand

View line C10

Vertaizon 13:27 → Clermont-Ferrand 13:45 Mon, Tue 0 h 18 min · 4 stops SNCF

It does not run today

Last recorded run: Friday 30 October 0 min

Next service: Monday 13:27 from Vertaizon · Mon 23 Nov

Next departure 13:27 Monday · Vertaizon
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 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 Clermont-Ferrand, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
13:27on time on time
13:30 / 13:31≈ on time ≈ on time
13:36 / 13:37≈ on time ≈ on time
13:45on 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 30 OctClermont-Ferrand 13:460 min—
Thu 29 OctClermont-Ferrand 13:460 min—
Wed 28 OctClermont-Ferrand 13:460 min—
Tue 27 OctClermont-Ferrand 13:460 min—
Mon 26 OctClermont-Ferrand 13:460 min—
Fri 23 OctClermont-Ferrand 13:460 min—
Thu 22 OctClermont-Ferrand 13:460 min—
Wed 21 OctClermont-Ferrand 13:460 min—
Tue 20 OctClermont-Ferrand 13:470 min—
Mon 19 OctClermont-Ferrand 13:460 min—
Fri 16 OctClermont-Ferrand 13:460 min—
Thu 15 OctClermont-Ferrand 13:460 min—
Wed 14 OctClermont-Ferrand 13:460 min—
Tue 13 OctClermont-Ferrand 13:460 min—
Mon 12 OctClermont-Ferrand 13:460 min—
Fri 9 OctClermont-Ferrand 13:460 min—
Thu 8 OctClermont-Ferrand 13:460 min—
Wed 7 OctClermont-Ferrand 13:460 min—
Tue 6 OctClermont-Ferrand 13:460 min—
Mon 5 OctClermont-Ferrand 13:460 min—
Fri 28 AugStopPoint:OCETrain TER-8773400 13:440 min—
Thu 27 AugStopPoint:OCETrain TER-8773400 13:440 min—
Wed 26 AugStopPoint:OCETrain TER-8773400 13:440 min—
Tue 25 AugStopPoint:OCETrain TER-8773400 13:450 min—
Mon 24 AugStopPoint:OCETrain TER-8773400 13:440 min—
Fri 21 AugStopPoint:OCETrain TER-8773400 13:440 min—
Thu 20 AugStopPoint:OCETrain TER-8773400 13:440 min—