R91 30339 Leuk → Brig
Alerts for train 30339
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R91.
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).
An alert on this phone or computer when the 30339 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today it reached Brig at 01:30 0 min
- Leuk01:08
- Turtmann01:11
- Gampel-Steg01:14
- Raron01:18
- Visp01:22
- Brig01:30
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 01:08 | on 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:30 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Brig 01:29 | 0 min | — |
| Sun 15 Nov | Brig 01:29 | No data | — |
| Sun 8 Nov | Visp 13:34 | −1 min | — |
| Sat 7 Nov | Visp 13:34 | 0 min | — |
| Fri 6 Nov | Visp 13:33 | −1 min | — |
| Thu 5 Nov | Visp 13:34 | No data | — |
| Wed 4 Nov | Visp 13:34 | 0 min | — |
| Tue 3 Nov | Visp 13:34 | 0 min | — |
| Mon 2 Nov | Visp 13:34 | 0 min | — |
| Sun 1 Nov | Visp 13:33 | −1 min | — |
| Sat 31 Oct | Visp 13:34 | 0 min | — |
| Fri 30 Oct | Visp 13:33 | −1 min | — |
| Thu 29 Oct | Visp 13:34 | No data | — |
| Wed 28 Oct | Visp 13:35 | +1 min | — |
| Tue 27 Oct | Visp 13:34 | 0 min | — |
| Mon 26 Oct | Visp 13:34 | No data | — |
| Sun 25 Oct | Visp 13:34 | 0 min | — |
| Sat 24 Oct | Visp 13:34 | 0 min | — |
| Fri 23 Oct | Visp 13:34 | +1 min | — |
| Thu 22 Oct | Visp 13:34 | No data | — |
| Wed 21 Oct | Visp 13:35 | +1 min | — |
| Tue 20 Oct | Visp 13:34 | −1 min | — |
| Mon 19 Oct | Visp 13:34 | −1 min | — |
| Sun 18 Oct | Visp 13:33 | −2 min | — |
| Sat 17 Oct | Visp 13:34 | 0 min | — |
| Fri 16 Oct | Visp 13:33 | −1 min | — |
| Thu 15 Oct | Visp 13:34 | −1 min | — |
| Wed 14 Oct | Visp 13:34 | 0 min | — |
| Tue 13 Oct | Visp 13:35 | +1 min | — |
| Mon 12 Oct | Visp 13:34 | No data | — |