R91 30339 Leuk → Brig

View line R91

Leuk 01:08 → Brig 01:30 Sat 0 h 22 min · 6 stops Regionalps

R91 30339 Leuk–Brig: final delay under 3 min on 14 of its 14 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:43 (GMT+1).

✓ Today’s run finished

Today it reached Brig at 01:30 0 min

  1. Leuk01:08
  2. Turtmann01:11
  3. Gampel-Steg01:14
  4. Raron01:18
  5. Visp01:22
  6. Brig01:30
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 4 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Brig, 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

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

  • Early 8% · 2
  • On time 92% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=4
  • 100% T n=1
  • 100% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 24 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
01:08on time on time
01:11≈ on time ≈ on time
01:14 / 01:15≈ on time ≈ on time
01:18≈ on time ≈ on time
01:22 / 01:23≈ on time ≈ on time
01:30on time +1 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 22 NovBrig 01:290 min—
Sun 15 NovBrig 01:29No data—
Sun 8 NovVisp 13:34−1 min—
Sat 7 NovVisp 13:340 min—
Fri 6 NovVisp 13:33−1 min—
Thu 5 NovVisp 13:34No data—
Wed 4 NovVisp 13:340 min—
Tue 3 NovVisp 13:340 min—
Mon 2 NovVisp 13:340 min—
Sun 1 NovVisp 13:33−1 min—
Sat 31 OctVisp 13:340 min—
Fri 30 OctVisp 13:33−1 min—
Thu 29 OctVisp 13:34No data—
Wed 28 OctVisp 13:35+1 min—
Tue 27 OctVisp 13:340 min—
Mon 26 OctVisp 13:34No data—
Sun 25 OctVisp 13:340 min—
Sat 24 OctVisp 13:340 min—
Fri 23 OctVisp 13:34+1 min—
Thu 22 OctVisp 13:34No data—
Wed 21 OctVisp 13:35+1 min—
Tue 20 OctVisp 13:34−1 min—
Mon 19 OctVisp 13:34−1 min—
Sun 18 OctVisp 13:33−2 min—
Sat 17 OctVisp 13:340 min—
Fri 16 OctVisp 13:33−1 min—
Thu 15 OctVisp 13:34−1 min—
Wed 14 OctVisp 13:340 min—
Tue 13 OctVisp 13:35+1 min—
Mon 12 OctVisp 13:34No data—