F27 868472 Brive-la-Gaillarde – Tulle

View line F27

Brive-la-Gaillarde 17:46 → Tulle 18:11 Mon, Tue, Wed, Thu 0 h 25 min · 4 stops SNCF

It does not run today

Last recorded run: Thursday 5 November No data

Next service: tomorrow 17:46 from Brive-la-Gaillarde · Mon 9 Nov

Next departure 17:46 tomorrow · Brive-la-Gaillarde
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 1 no data
On-time · 90 days
88%
42/48 runs under 3 min
RT coverage: 48 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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 17 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8759449 +25 min
  • Wed 21 Oct Max en route +10 min · last fix heading to Tulle +10 min
  • Thu 27 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8759448 +10 min
  • Wed 26 Aug Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8759448 +10 min
  • Mon 28 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8759449 +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 42
  • 3–10 min 4% · 2
  • 10–30 min 8% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=12
  • 100% T n=13
  • 83% W n=12
  • 82% T n=11
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 48 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
17:46on time on time
17:54 / 17:55≈ on time ≈ +2 min
18:02 / 18:03≈ on time ≈ +4 min
18:11on time +5 min

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
Thu 5 NovTulle 18:12No data—
Wed 4 NovTulle 18:120 min—
Tue 3 NovTulle 18:130 min—
Mon 2 NovTulle 18:120 min—
Thu 29 OctTulle 18:120 min—
Wed 28 OctTulle 18:120 min—
Tue 27 OctTulle 18:120 min—
Mon 26 OctTulle 18:130 min—
Thu 22 OctTulle 18:130 min—
Wed 21 OctTulle 18:23+10 min+10 min
Tue 20 OctTulle 18:120 min—
Mon 19 OctTulle 18:120 min—
Thu 15 OctTulle 18:120 min—
Wed 14 OctTulle 18:120 min—
Tue 13 OctTulle 18:120 min—
Mon 12 OctTulle 18:120 min—
Thu 8 OctTulle 18:130 min—
Wed 7 OctTulle 18:120 min—
Tue 6 OctTulle 18:120 min—
Mon 5 OctTulle 18:120 min—
Thu 1 OctStopPoint:OCETrain TER-8759449 18:110 min—
Wed 30 SeptStopPoint:OCETrain TER-8759449 18:100 min—
Tue 29 SeptStopPoint:OCETrain TER-8759449 18:100 min—
Mon 28 SeptStopPoint:OCETrain TER-8759449 18:10+5 min+5 min
Thu 24 SeptStopPoint:OCETrain TER-8759449 18:110 min+15 min
Wed 23 SeptStopPoint:OCETrain TER-8759449 18:100 min—
Tue 22 SeptStopPoint:OCETrain TER-8759449 18:100 min—
Mon 21 SeptStopPoint:OCETrain TER-8759449 18:10+5 min+5 min
Thu 17 SeptStopPoint:OCETrain TER-8759449 18:10+25 min+25 min
Wed 16 SeptStopPoint:OCETrain TER-8759449 18:100 min—