L26 868600 Limoges Bénédictins – Ussel

View line L26

Limoges Bénédictins 05:37 → Ussel 07:27 Mon, Tue, Wed, Thu, Fri 1 h 50 min · 13 stops SNCF

✓ Today’s run finished

Today it reached Ussel at 07:27 0 min

  1. Limoges Bénédictins05:37
  2. Brignac05:52
  3. Saint-Denis-des-Murs06:07
  4. Eymoutiers Vassivière06:26
  5. Bugeat06:49
  6. Jassonneix07:11
  7. Ussel07:27

Next service: tomorrow 05:37 from Limoges Bénédictins · Tue 17 Nov

Next departure 05:37 tomorrow · Limoges Bénédictins
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 29 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: +1 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

  • Thu 12 Nov Max en route +5 min · last fix heading to Ussel +5 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Ussel +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 83% T n=6
  • 100% W n=5
  • 80% T n=5
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
05:37on time on time
05:47 / 05:48≈ on time ≈ on time
05:52 / 05:53≈ on time ≈ on time
05:58 / 06:00≈ on time ≈ on time
06:07 / 06:08≈ on time ≈ on time
06:16 / 06:17≈ on time ≈ on time
06:26 / 06:27≈ on time ≈ on time
06:40 / 06:41≈ on time ≈ on time
06:49 / 06:50≈ on time ≈ on time
06:56≈ on time ≈ on time
07:11≈ on time ≈ on time
07:14 / 07:15≈ on time ≈ on time
07:27on 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
Mon 16 NovUssel 07:280 min—
Fri 13 NovUssel 07:280 min—
Thu 12 NovUssel 07:33+5 min+5 min
Tue 10 NovUssel 07:280 min—
Mon 9 NovUssel 07:280 min—
Fri 6 NovUssel 07:290 min—
Thu 5 NovUssel 07:28No data—
Wed 4 NovUssel 07:280 min—
Tue 3 NovUssel 07:33+5 min+5 min
Mon 2 NovUssel 07:280 min—
Fri 30 OctUssel 07:280 min—
Thu 29 OctUssel 07:280 min—
Wed 28 OctUssel 07:280 min—
Tue 27 OctUssel 07:280 min—
Mon 26 OctUssel 07:280 min—
Fri 23 OctUssel 07:280 min—
Thu 22 OctUssel 07:280 min—
Wed 21 OctUssel 07:280 min—
Tue 20 OctUssel 07:280 min—
Mon 19 OctUssel 07:280 min—
Fri 16 OctUssel 07:290 min—
Thu 15 OctUssel 07:290 min—
Wed 14 OctUssel 07:280 min—
Tue 13 OctUssel 07:280 min—
Mon 12 OctUssel 07:280 min—
Fri 9 OctUssel 07:290 min—
Thu 8 OctUssel 07:280 min—
Wed 7 OctUssel 07:290 min—
Tue 6 OctUssel 07:290 min—
Mon 5 OctStopPoint:OCETrain TE~ef9bfbde 07:290 min—