F27 868478 Brive-la-Gaillarde – Tulle

View line F27

Brive-la-Gaillarde 17:50 → Tulle 18:17 Wed, Sun 0 h 27 min · 4 stops SNCF

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 17:50 from Brive-la-Gaillarde · Sun 8 Nov

Next departure 17:50 today · Brive-la-Gaillarde
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

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

  • Sun 6 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8759448 +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 0% · 0
  • 10–30 min 11% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 89% S n=9

Stops and timetable

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

Last 90 days, 9 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:50on time on time
17:59 / 18:01≈ on time ≈ +1 min
18:08 / 18:09≈ on time ≈ +1 min
18:17on time +2 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
Sun 1 NovTulle 18:180 min—
Sun 25 OctTulle 18:180 min—
Sun 18 OctTulle 18:190 min—
Sun 11 OctTulle 18:180 min—
Sun 4 OctStopPoint:OCETrain TE~92f35ebb 18:180 min—
Wed 30 SeptStopPoint:OCETrain TER-8759449 18:16No data—
Wed 23 SeptStopPoint:OCETrain TER-8759449 18:16No data—
Sun 20 SeptStopPoint:OCETrain TER-8759449 18:170 min+5 min
Wed 16 SeptStopPoint:OCETrain TER-8759449 18:16No data—
Sun 13 SeptStopPoint:OCETrain TER-8759449 18:160 min+25 min
Wed 9 SeptStopPoint:OCETrain TER-8759449 18:16No data—
Sun 6 SeptStopPoint:OCETrain TER-8759448 18:16+10 min+10 min
Wed 26 AugStopPoint:OCETrain TER-8759449 18:16No data—
Sun 16 AugStopPoint:OCETrain TER-8759449 18:170 min+10 min