L23 868366 Brive-la-Gaillarde – Objat

View line L23

Brive-la-Gaillarde 15:20 → Objat 15:51 Wed, Sun 0 h 31 min · 5 stops SNCF

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: tomorrow 15:20 from Brive-la-Gaillarde · Wed 11 Nov

Next departure 15:20 tomorrow · Brive-la-Gaillarde
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Objat, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
15:20on time on time
15:34 / 15:35≈ on time ≈ on time
15:39 / 15:40≈ on time ≈ on time
15:46 / 15:47≈ on time ≈ on time
15: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
Sun 8 NovObjat 15:520 min—
Sun 1 NovObjat 15:520 min—
Sun 25 OctObjat 15:520 min—
Sun 18 OctObjat 15:520 min—
Sun 11 OctObjat 15:520 min—
Sun 4 OctStopPoint:OCETrain TE~3781b060 15:520 min—
Wed 30 SeptStopPoint:OCETrain TER-8759463 15:50No data—
Sun 27 SeptStopPoint:OCETrain TER-8759463 15:500 min+10 min
Wed 23 SeptStopPoint:OCETrain TER-8759463 15:50No data—
Sun 20 SeptStopPoint:OCETrain TER-8759463 15:510 min—
Wed 16 SeptStopPoint:OCETrain TER-8759463 15:51No data—
Sun 13 SeptStopPoint:OCETrain TER-8759463 15:500 min—
Wed 9 SeptStopPoint:OCETrain TER-8759463 15:50No data—
Sun 6 SeptStopPoint:OCETrain TER-8759463 15:500 min—
Wed 2 SeptStopPoint:OCETrain TER-8759463 15:51No data—
Sun 30 AugStopPoint:OCETrain TER-8759463 15:500 min—
Wed 26 AugStopPoint:OCETrain TER-8759463 15:50No data—
Sun 23 AugStopPoint:OCETrain TER-8759463 15:500 min—
Wed 19 AugStopPoint:OCETrain TER-8759463 15:50No data—
Sun 16 AugStopPoint:OCETrain TER-8759463 15:510 min—