P12 870163 Brive-la-Gaillarde – Rodez

View line P12

Brive-la-Gaillarde 17:07 → Rodez 19:47 Mon, Tue, Wed, Thu, Fri 2 h 40 min · 13 stops SNCF

It has not run yet today

Last recorded run: Monday 16 November +5 min

Next service: today 17:07 from Brive-la-Gaillarde · Tue 17 Nov

Next departure 17:07 today · Brive-la-Gaillarde
On-time · 30 days
74%
14/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Tue 27 Oct Max en route +20 min · last fix heading to Rodez +20 min
  • Fri 30 Oct Max en route +15 min · last fix heading to Rodez +15 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Rodez +5 min
  • Fri 13 Nov Max en route +10 min · last fix heading to Rodez +5 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Rodez +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 24
  • 3–10 min 10% · 3
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 83% T n=6
  • 80% W n=5
  • 100% T n=5
  • 67% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
17:07on time on time
17:20 / 17:31≈ on time ≈ +1 min
17:40 / 17:41≈ on time ≈ +1 min
17:59 / 18:00≈ on time ≈ +2 min
18:06 / 18:07≈ on time ≈ +2 min
18:17 / 18:18≈ on time ≈ +3 min
18:33 / 18:34≈ on time ≈ +3 min
18:41 / 18:44≈ on time ≈ +3 min
18:58 / 18:59≈ on time ≈ +4 min
19:03 / 19:04≈ on time ≈ +4 min
19:07 / 19:08≈ on time ≈ +4 min
19:19 / 19:20≈ on time ≈ +4 min
19:47on time +5 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
Mon 16 NovRodez 19:53+5 min+5 min
Fri 13 NovRodez 19:54+5 min+10 min
Thu 12 NovRodez 19:480 min—
Tue 10 NovRodez 19:480 min—
Mon 9 NovRodez 19:480 min—
Fri 6 NovRodez 19:490 min—
Thu 5 NovRodez 19:49No data—
Wed 4 NovRodez 19:480 min—
Tue 3 NovRodez 19:490 min—
Mon 2 NovRodez 19:480 min—
Fri 30 OctRodez 20:03+15 min+15 min
Thu 29 OctRodez 19:480 min—
Wed 28 OctRodez 19:53+5 min+5 min
Tue 27 OctRodez 20:08+20 min+20 min
Mon 26 OctRodez 19:490 min—
Fri 23 OctRodez 19:490 min—
Thu 22 OctRodez 19:480 min—
Wed 21 OctRodez 19:480 min—
Tue 20 OctRodez 19:480 min—
Mon 19 OctRodez 19:480 min—
Fri 16 OctRodez 19:480 min—
Thu 15 OctRodez 19:480 min—
Wed 14 OctRodez 19:480 min—
Tue 13 OctRodez 19:480 min—
Mon 12 OctRodez 19:480 min—
Fri 9 OctRodez 19:480 min—
Thu 8 OctRodez 19:480 min—
Wed 7 OctRodez 19:480 min—
Tue 6 OctRodez 19:480 min—
Mon 5 OctRodez 19:480 min—