F27 868467 Tulle → Brive-la-Gaillarde

View line F27

Tulle 17:02 → Brive-la-Gaillarde 17:30 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 4 stops SNCF

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 17:02 from Tulle · Mon 23 Nov

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=6
  • 100% 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, 33 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:02on time on time
17:09 / 17:10≈ on time ≈ on time
17:17 / 17:19≈ on time ≈ on time
17:30on 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 NovBrive-la-Gaillarde 17:290 min—
Thu 19 NovBrive-la-Gaillarde 17:290 min—
Wed 18 NovBrive-la-Gaillarde 17:290 min—
Tue 17 NovBrive-la-Gaillarde 17:290 min—
Mon 16 NovBrive-la-Gaillarde 17:320 min—
Fri 13 NovBrive-la-Gaillarde 17:300 min—
Thu 12 NovBrive-la-Gaillarde 17:290 min—
Tue 10 NovBrive-la-Gaillarde 17:290 min—
Mon 9 NovBrive-la-Gaillarde 17:290 min—
Fri 6 NovBrive-la-Gaillarde 17:290 min—
Thu 5 NovBrive-la-Gaillarde 17:290 min—
Wed 4 NovBrive-la-Gaillarde 17:290 min—
Tue 3 NovBrive-la-Gaillarde 17:320 min—
Mon 2 NovBrive-la-Gaillarde 17:290 min—
Fri 30 OctBrive-la-Gaillarde 17:310 min—
Thu 29 OctBrive-la-Gaillarde 17:310 min—
Wed 28 OctBrive-la-Gaillarde 17:310 min—
Tue 27 OctBrive-la-Gaillarde 17:310 min—
Mon 26 OctBrive-la-Gaillarde 17:320 min—
Fri 23 OctBrive-la-Gaillarde 17:320 min—
Wed 21 OctBrive-la-Gaillarde 17:320 min—
Tue 20 OctBrive-la-Gaillarde 17:310 min—
Mon 19 OctBrive-la-Gaillarde 17:320 min—
Fri 16 OctBrive-la-Gaillarde 17:310 min—
Thu 15 OctBrive-la-Gaillarde 17:310 min—
Wed 14 OctBrive-la-Gaillarde 17:310 min—
Tue 13 OctBrive-la-Gaillarde 17:310 min—
Mon 12 OctBrive-la-Gaillarde 17:310 min—
Fri 9 OctBrive-la-Gaillarde 17:310 min—
Thu 8 OctBrive-la-Gaillarde 17:310 min—