P12 870159 Capdenac – Rodez

View line P12

Capdenac 12:43 → Rodez 13:46 Mon, Tue, Wed, Thu, Fri 1 h 03 min · 6 stops SNCF

It does not run today

Last recorded run: Friday 13 November +15 min

Next service: tomorrow 12:43 from Capdenac · Mon 16 Nov

Next departure 12:43 tomorrow · Capdenac
On-time · 30 days
29%
5/17 runs under 3 min
RT coverage: 17 full · 0 partial · 3 no data
On-time · 90 days
50%
17/34 runs under 3 min
RT coverage: 34 full · 0 partial · 4 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +10 min
P90
+18min
9 in 10 runs arrive with less than this
30 days: +20 min

Last 30 days

Arrival delay at Rodez, in minutes. One bar per run.

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

Worst days

  • Wed 21 Oct Max en route +80 min · last fix heading to Rodez +80 min
  • Thu 22 Oct Max en route +20 min · last fix heading to Rodez +20 min
  • Tue 20 Oct Max en route +20 min · last fix heading to Rodez +20 min
  • Wed 9 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8761342 +20 min
  • Fri 13 Nov Max en route +15 min · last fix heading to Rodez +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 50% · 17
  • 3–10 min 18% · 6
  • 10–30 min 29% · 10
  • 30+ min 3% · 1

On-time by weekday

  • 71% M n=7
  • 43% T n=7
  • 25% W n=8
  • 67% T n=6
  • 50% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
12:43on time +9 min
12:57 / 12:58≈ +1 min ≈ +8 min
13:02≈ +2 min ≈ +8 min
13:05 / 13:06≈ +2 min ≈ +8 min
13:18 / 13:19≈ +3 min ≈ +11 min
13:46on time +19 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 13 NovRodez 13:47+15 min+15 min
Thu 12 NovRodez 13:470 min—
Wed 11 NovRodez 13:47No data—
Tue 10 NovRodez 13:47+5 min+5 min
Mon 9 NovRodez 13:480 min—
Fri 6 NovRodez 13:470 min—
Thu 5 NovRodez 13:47No data—
Wed 4 NovRodez 13:57+10 min+10 min
Tue 3 NovRodez 13:53+5 min+5 min
Mon 2 NovRodez 13:470 min—
Fri 30 OctRodez 13:52+5 min+5 min
Thu 29 OctRodez 13:57+10 min+10 min
Wed 28 OctRodez 14:02+15 min+20 min
Tue 27 OctRodez 13:47No data—
Mon 26 OctRodez 13:470 min—
Fri 23 OctRodez 13:57+10 min+10 min
Thu 22 OctRodez 14:07+20 min+20 min
Wed 21 OctRodez 15:07+80 min+80 min
Tue 20 OctRodez 14:08+20 min+20 min
Mon 19 OctRodez 13:57+10 min+10 min
Fri 16 OctRodez 13:470 min—
Thu 15 OctRodez 13:470 min—
Wed 14 OctRodez 13:470 min—
Tue 13 OctRodez 13:470 min—
Mon 12 OctRodez 13:470 min—
Fri 9 OctRodez 13:470 min—
Thu 8 OctRodez 13:470 min—
Wed 7 OctRodez 13:470 min—
Tue 6 OctRodez 13:52+5 min+5 min
Mon 5 OctRodez 13:460 min—