F27 868452 Brive-la-Gaillarde → Tulle

View line F27

Brive-la-Gaillarde 07:02 → Tulle 07:29 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 4 stops SNCF

TER 868452 Brive-la-Gaillarde–Tulle: final delay under 3 min on 15 of its 15 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 03:41 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 07:02 from Brive-la-Gaillarde · Mon 23 Nov

Next departure 07:02 tomorrow · Brive-la-Gaillarde
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 1 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 30 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 Tulle, in minutes. One bar per run.

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

Worst days

  • Mon 19 Oct Max en route +5 min · last fix heading to Tulle +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Tulle +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 80% W n=5
  • 100% T n=4
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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
07:02on time on time
07:11 / 07:13≈ on time ≈ on time
07:20 / 07:21≈ on time ≈ on time
07:29on 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 20 NovTulle 07:290 min—
Tue 17 NovTulle 07:290 min—
Mon 16 NovTulle 07:290 min—
Fri 13 NovTulle 07:290 min—
Thu 12 NovTulle 07:290 min—
Tue 10 NovTulle 07:290 min—
Mon 9 NovTulle 07:290 min—
Fri 6 NovTulle 07:290 min—
Thu 5 NovTulle 07:29No data—
Wed 4 NovTulle 07:290 min—
Tue 3 NovTulle 07:290 min—
Mon 2 NovTulle 07:290 min—
Fri 30 OctTulle 07:300 min—
Wed 28 OctTulle 07:300 min—
Tue 27 OctTulle 07:300 min—
Mon 26 OctTulle 07:300 min—
Fri 23 OctTulle 07:300 min—
Thu 22 OctTulle 07:300 min—
Wed 21 OctTulle 07:300 min—
Tue 20 OctTulle 07:300 min—
Mon 19 OctTulle 07:35+5 min+5 min
Fri 16 OctTulle 07:310 min—
Thu 15 OctTulle 07:310 min—
Wed 14 OctTulle 07:300 min—
Tue 13 OctTulle 07:300 min—
Mon 12 OctTulle 07:300 min—
Fri 9 OctTulle 07:310 min—
Thu 8 OctTulle 07:300 min—
Wed 7 OctTulle 07:36+5 min+5 min
Tue 6 OctTulle 07:310 min—