P12 870161 Brive-la-Gaillarde – Rodez

View line P12

Brive-la-Gaillarde 14:35 → Rodez 17:09 Mon, Tue, Wed, Thu, Fri 2 h 34 min · 13 stops SNCF

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 14:35 from Brive-la-Gaillarde · Thu 19 Nov

Next departure 14:35 today · Brive-la-Gaillarde
On-time · 30 days
53%
10/19 runs under 3 min
RT coverage: 19 full · 0 partial · 2 no data
On-time · 90 days
64%
35/55 runs under 3 min
RT coverage: 55 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+15min
9 in 10 runs arrive with less than this
30 days: +15 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 +60 min · last fix heading to Rodez +60 min
  • Wed 9 Sept Max en route +40 min · last fix heading to StopPoint:OCETrain TER-8761325 +35 min
  • Thu 10 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8761342 +20 min
  • Mon 9 Nov Max en route +20 min · last fix heading to Rodez +15 min
  • Tue 3 Nov Max en route +20 min · last fix heading to Rodez +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 64% · 35
  • 3–10 min 11% · 6
  • 10–30 min 22% · 12
  • 30+ min 4% · 2

On-time by weekday

  • 85% M n=13
  • 54% T n=13
  • 55% W n=11
  • 55% T n=11
  • 71% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 55 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
14:35on time on time
14:47 / 14:48≈ on time ≈ +4 min
14:58 / 15:01≈ on time ≈ +6 min
15:20 / 15:21≈ on time ≈ +8 min
15:27 / 15:28≈ on time ≈ +8 min
15:38 / 15:39≈ on time ≈ +8 min
15:54 / 15:55≈ on time ≈ +9 min
16:02 / 16:07≈ on time ≈ +10 min
16:21 / 16:22≈ on time ≈ +11 min
16:26≈ on time ≈ +12 min
16:29 / 16:30≈ on time ≈ +12 min
16:41 / 16:42≈ on time ≈ +13 min
17:09on time +15 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
Wed 18 NovRodez 17:090 min—
Tue 17 NovRodez 17:19+10 min+10 min
Mon 16 NovRodez 17:090 min—
Fri 13 NovRodez 17:100 min—
Thu 12 NovRodez 17:14+5 min+5 min
Wed 11 NovRodez 17:09No data—
Tue 10 NovRodez 17:090 min—
Mon 9 NovRodez 17:24+15 min+20 min
Fri 6 NovRodez 17:090 min—
Thu 5 NovRodez 17:09No data—
Wed 4 NovRodez 17:090 min—
Tue 3 NovRodez 17:25+15 min+20 min
Mon 2 NovRodez 17:090 min—
Fri 30 OctRodez 17:25+15 min+15 min
Thu 29 OctRodez 17:100 min—
Wed 28 OctRodez 17:15+5 min+5 min
Tue 27 OctRodez 18:10+60 min+60 min
Mon 26 OctRodez 17:110 min—
Fri 23 OctRodez 17:26+15 min+20 min
Thu 22 OctRodez 17:110 min+10 min
Wed 21 OctRodez 17:15+5 min+5 min
Tue 20 OctRodez 17:20+10 min+10 min
Mon 19 OctRodez 17:110 min—
Fri 16 OctRodez 17:100 min—
Thu 15 OctRodez 17:100 min—
Wed 14 OctRodez 17:100 min—
Tue 13 OctRodez 17:100 min—
Mon 12 OctRodez 17:100 min—
Fri 9 OctRodez 17:100 min—
Thu 8 OctRodez 17:100 min—