F27 868462 Brive-la-Gaillarde → Tulle

View line F27

Brive-la-Gaillarde 11:23 → Tulle 11:48 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 4 stops SNCF

TER 868462 Brive-la-Gaillarde–Tulle: final delay under 3 min on 16 of its 17 runs with data in the last 30 days (94%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:06 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

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

Next departure 11:23 tomorrow · Brive-la-Gaillarde
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 32 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

  • Thu 19 Nov Max en route +5 min · last fix heading to Tulle +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=5
  • 83% T n=6
  • 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, 32 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
11:23on time on time
11:31 / 11:32≈ on time ≈ on time
11:39 / 11:40≈ on time ≈ on time
11:48on 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 11:490 min+5 min
Thu 19 NovTulle 11:53+5 min+5 min
Tue 17 NovTulle 11:490 min—
Mon 16 NovTulle 11:490 min—
Fri 13 NovTulle 11:490 min—
Thu 12 NovTulle 11:490 min—
Tue 10 NovTulle 11:490 min—
Mon 9 NovTulle 11:490 min—
Fri 6 NovTulle 11:490 min—
Thu 5 NovTulle 11:49No data—
Wed 4 NovTulle 11:490 min—
Tue 3 NovTulle 11:490 min—
Mon 2 NovTulle 11:490 min—
Fri 30 OctTulle 11:490 min—
Thu 29 OctTulle 11:490 min—
Wed 28 OctTulle 11:490 min—
Tue 27 OctTulle 11:490 min—
Mon 26 OctTulle 11:490 min—
Fri 23 OctTulle 11:490 min—
Thu 22 OctTulle 11:490 min—
Wed 21 OctTulle 11:490 min—
Tue 20 OctTulle 11:500 min—
Mon 19 OctTulle 11:500 min—
Fri 16 OctTulle 11:490 min—
Thu 15 OctTulle 11:490 min—
Wed 14 OctTulle 11:490 min—
Tue 13 OctTulle 11:490 min—
Mon 12 OctTulle 11:500 min—
Fri 9 OctTulle 11:500 min—
Thu 8 OctTulle 11:490 min—