L23 868360 Brive-la-Gaillarde – Objat

View line L23

Brive-la-Gaillarde 12:37 → Objat 13:08 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 5 stops SNCF

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 12:37 from Brive-la-Gaillarde · Thu 5 Nov

Next departure 12:37 today · Brive-la-Gaillarde
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 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 Objat, in minutes. One bar per run.

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

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to Objat +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 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=4
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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:37on time on time
12:50 / 12:51≈ on time ≈ on time
12:56 / 12:57≈ on time ≈ on time
13:02 / 13:03≈ on time ≈ on time
13:08on 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
Wed 4 NovObjat 13:090 min—
Tue 3 NovObjat 13:090 min—
Mon 2 NovObjat 13:090 min—
Fri 30 OctObjat 13:090 min—
Thu 29 OctObjat 13:090 min—
Wed 28 OctObjat 13:090 min—
Tue 27 OctObjat 13:090 min—
Mon 26 OctObjat 13:090 min—
Fri 23 OctObjat 13:090 min—
Thu 22 OctObjat 13:090 min—
Wed 21 OctObjat 13:090 min—
Tue 20 OctObjat 13:100 min—
Mon 19 OctObjat 13:090 min—
Fri 16 OctObjat 13:090 min—
Thu 15 OctObjat 13:090 min—
Wed 14 OctObjat 13:090 min—
Tue 13 OctObjat 13:090 min—
Mon 12 OctObjat 13:090 min—
Fri 9 OctObjat 13:13+5 min+5 min
Thu 8 OctObjat 13:090 min—
Wed 7 OctObjat 13:090 min—
Tue 6 OctObjat 13:090 min—
Mon 5 OctStopPoint:OCETrain TE~3781b060 13:09Partial coverage0 min—