L26 868606 Limoges Bénédictins – Ussel

View line L26

Limoges Bénédictins 10:05 → Ussel 11:57 Daily 1 h 52 min · 13 stops SNCF

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 10:05 from Limoges Bénédictins · Thu 19 Nov

Next departure 10:05 today · Limoges Bénédictins
On-time · 30 days
82%
23/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
85%
44/52 runs under 3 min
RT coverage: 52 full · 0 partial · 1 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: +7 min

Last 30 days

Arrival delay at Ussel, in minutes. One bar per run.

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

Worst days

  • Wed 21 Oct Max en route +110 min · last fix heading to Ussel +110 min
  • Sat 24 Oct Max en route +40 min · last fix heading to Ussel +40 min
  • Tue 20 Oct Max en route +35 min · last fix heading to Ussel +35 min
  • Fri 30 Oct Max en route +10 min · last fix heading to Ussel +10 min
  • Fri 9 Oct Max en route +10 min · last fix heading to Ussel +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 44
  • 3–10 min 6% · 3
  • 10–30 min 4% · 2
  • 30+ min 6% · 3

On-time by weekday

  • 88% M n=8
  • 78% T n=9
  • 88% W n=8
  • 100% T n=6
  • 50% F n=6
  • 83% S n=6
  • 100% S n=9

Stops and timetable

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

Last 90 days, 52 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
10:05on time +5 min
10:15 / 10:16≈ on time ≈ +5 min
10:21 / 10:22≈ on time ≈ +5 min
10:27 / 10:29≈ on time ≈ +5 min
10:35 / 10:36≈ on time ≈ +5 min
10:45 / 10:46≈ on time ≈ +5 min
10:54 / 10:55≈ on time ≈ +5 min
11:09 / 11:10≈ on time ≈ +5 min
11:18 / 11:20≈ on time ≈ +5 min
11:26≈ on time ≈ +5 min
11:40≈ on time ≈ +5 min
11:44 / 11:45≈ on time ≈ +5 min
11:57on 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
Wed 18 NovUssel 11:580 min+5 min
Tue 17 NovUssel 11:580 min—
Mon 16 NovUssel 11:590 min—
Sun 15 NovUssel 11:590 min—
Sat 14 NovUssel 11:580 min—
Fri 13 NovUssel 11:580 min—
Thu 12 NovUssel 11:580 min—
Wed 11 NovUssel 11:580 min—
Tue 10 NovUssel 11:580 min+5 min
Mon 9 NovUssel 11:590 min—
Sun 8 NovUssel 11:580 min—
Sat 7 NovUssel 11:580 min—
Fri 6 NovUssel 11:580 min—
Thu 5 NovUssel 11:59No data—
Wed 4 NovUssel 11:580 min+5 min
Tue 3 NovUssel 12:03+5 min+5 min
Mon 2 NovUssel 11:580 min—
Sun 1 NovUssel 11:580 min—
Sat 31 OctUssel 11:580 min—
Fri 30 OctUssel 12:08+10 min+10 min
Thu 29 OctUssel 11:580 min—
Wed 28 OctUssel 11:580 min—
Tue 27 OctUssel 11:580 min—
Mon 26 OctUssel 11:580 min—
Sun 25 OctUssel 11:580 min—
Sat 24 OctUssel 12:38+40 min+40 min
Fri 23 OctUssel 12:03+5 min+5 min
Thu 22 OctUssel 11:580 min—
Wed 21 OctUssel 13:48+110 min+110 min
Tue 20 OctUssel 12:34+35 min+35 min