L23 868356 Brive-la-Gaillarde – Objat

View line L23

Brive-la-Gaillarde 06:16 → Objat 06:47 Mon, Tue, Thu, Fri, Sat 0 h 31 min · 5 stops SNCF

Running now · updated 06:46

Between Saint-Aulaire and Objat 0 min

Estimated arrival at Objat 06:47 · 28 km/h

  1. Brive-la-Gaillarde06:16
  2. Varetz06:30
  3. Le Burg06:36
  4. Saint-Aulaire06:42
  5. Objat06:47

Today it is running no worse than usual: typical arrival delay is 0 min; 96% of the last 23 runs arrived on time.

On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 1 no data
On-time · 90 days
97%
28/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

  • Thu 29 Oct Max en route +15 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 97% · 28
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=5
  • 75% T n=4
  • 100% F n=5
  • 100% S n=5
  • — 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 10Today
06:16on time on timePassed
06:30 / 06:31≈ on time ≈ on timePassed
06:36 / 06:37≈ on time ≈ on timePassed
06:42 / 06:43≈ on time ≈ on timePassed
06:47on time on timeNext

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 9 NovObjat 06:440 min—
Sat 7 NovObjat 06:480 min—
Fri 6 NovObjat 06:480 min—
Thu 5 NovObjat 06:48No data—
Wed 4 NovObjat 06:480 min—
Tue 3 NovObjat 06:480 min—
Mon 2 NovObjat 06:480 min—
Sat 31 OctObjat 06:480 min—
Fri 30 OctObjat 06:480 min—
Thu 29 OctObjat 06:58+10 min+15 min
Wed 28 OctObjat 06:480 min—
Tue 27 OctObjat 06:480 min—
Mon 26 OctObjat 06:480 min—
Sat 24 OctObjat 06:480 min—
Fri 23 OctObjat 06:480 min—
Thu 22 OctObjat 06:480 min—
Wed 21 OctObjat 06:480 min—
Mon 19 OctObjat 06:480 min—
Sat 17 OctObjat 06:480 min—
Fri 16 OctObjat 06:480 min—
Thu 15 OctObjat 06:480 min—
Wed 14 OctObjat 06:480 min—
Tue 13 OctObjat 06:480 min—
Mon 12 OctObjat 06:480 min—
Sat 10 OctObjat 06:480 min—
Fri 9 OctObjat 06:480 min—
Thu 8 OctObjat 06:480 min—
Wed 7 OctObjat 06:480 min—
Tue 6 OctObjat 06:490 min—
Mon 5 OctStopPoint:OCETrain TE~3781b060 06:490 min—