L23 868364 Brive-la-Gaillarde – Objat

View line L23

Brive-la-Gaillarde 13:54 → Objat 14:24 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 5 stops SNCF

✓ Today’s run finished

Today it reached Objat at 14:24 0 min

  1. Brive-la-Gaillarde13:54
  2. Varetz14:07
  3. Le Burg14:13
  4. Saint-Aulaire14:19
  5. Objat14:24

Next service: Monday 13:54 from Brive-la-Gaillarde · Mon 16 Nov

Next departure 13:54 Monday · Brive-la-Gaillarde
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
93%
27/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
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

  • Tue 25 Aug Max en route +15 min · last fix heading to StopPoint:OCETrain TER-8759461 +15 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Objat +10 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 93% · 27
  • 3–10 min 0% · 0
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 100% W n=6
  • 75% T n=4
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
13:54on time on time
14:07 / 14:08≈ on time ≈ on time
14:13 / 14:14≈ on time ≈ on time
14:19 / 14:20≈ on time ≈ on time
14:24on 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
Fri 13 NovObjat 14:240 min—
Thu 12 NovObjat 14:34+10 min+10 min
Tue 10 NovObjat 14:240 min—
Mon 9 NovObjat 14:240 min—
Fri 6 NovObjat 14:240 min—
Thu 5 NovObjat 14:24No data—
Wed 4 NovObjat 14:240 min—
Tue 3 NovObjat 14:240 min—
Mon 2 NovObjat 14:240 min—
Fri 30 OctObjat 14:250 min—
Thu 29 OctObjat 14:250 min—
Wed 28 OctObjat 14:250 min—
Tue 27 OctObjat 14:250 min—
Mon 26 OctObjat 14:250 min—
Fri 23 OctObjat 14:250 min—
Wed 21 OctObjat 14:250 min—
Tue 20 OctObjat 14:250 min—
Mon 19 OctObjat 14:260 min—
Fri 16 OctObjat 14:250 min—
Thu 15 OctObjat 14:250 min—
Wed 14 OctObjat 14:250 min—
Tue 13 OctObjat 14:250 min—
Mon 12 OctObjat 14:250 min—
Fri 9 OctObjat 14:250 min—
Thu 8 OctObjat 14:250 min—
Wed 7 OctObjat 14:250 min—
Tue 6 OctObjat 14:250 min—
Mon 5 OctObjat 14:250 min—
Tue 25 AugStopPoint:OCETrain TER-8759461 14:24+15 min+15 min
Wed 19 AugStopPoint:OCETrain TER-8759463 14:230 min—