R91 6100 Brig → Sion
Alerts for train 6100
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.
✓ Today’s run finished
Today it reached Sion at 05:19 0 min
- Brig04:38
- Raron04:49
- Gampel-Steg04:53
- Leuk05:00
- Salgesch05:04
- St-Léonard05:14
- Sion05:19
Next service: tomorrow 04:38 from Brig · Sun 22 Nov
Last 30 days
Arrival delay at Sion, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 14 Nov Max en route +8 min · last fix heading to Sion +8 min
- Sun 25 Oct Max en route +5 min · last fix heading to Sion +5 min
- Sat 17 Oct Max en route +4 min · last fix heading to Sion +4 min
- Wed 18 Nov Max en route +4 min · last fix heading to Sion +4 min
- Sat 24 Oct Max en route +4 min · last fix heading to Sion +4 min
Distribution · 90 days
50 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 40
- 3–10 min 20% · 10
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 71% T n=7
- 57% W n=7
- 86% T n=7
- 100% F n=7
- 57% S n=7
- 86% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 50 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 |
|---|---|---|---|
| 04:38 | on time | on time | |
| 04:44 / 04:45 | ≈ on time | ≈ on time | |
| 04:49 | ≈ on time | ≈ +1 min | |
| 04:53 | ≈ on time | ≈ +1 min | |
| 04:56 | ≈ on time | ≈ +2 min | |
| 05:00 | ≈ on time | ≈ +2 min | |
| 05:04 | ≈ on time | ≈ +3 min | |
| 05:07 | ≈ on time | ≈ +3 min | |
| 05:14 | ≈ +1 min | ≈ +4 min | |
| 05:19 | +1 min | +4 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 |
|---|---|---|---|
| Sat 21 Nov | Sion 05:19 | 0 min | — |
| Fri 20 Nov | Sion 05:19 | 0 min | — |
| Thu 19 Nov | Sion 05:23 | +3 min | +3 min |
| Wed 18 Nov | Sion 05:24 | +4 min | +4 min |
| Tue 17 Nov | Sion 05:23 | +4 min | +4 min |
| Mon 16 Nov | Sion 05:22 | +2 min | +2 min |
| Sun 15 Nov | Sion 05:19 | 0 min | — |
| Sat 14 Nov | Sion 05:28 | +8 min | +8 min |
| Fri 13 Nov | Sion 05:20 | −1 min | — |
| Thu 12 Nov | Sion 05:22 | +2 min | +2 min |
| Wed 11 Nov | Sion 05:19 | 0 min | — |
| Tue 10 Nov | Sion 05:22 | +2 min | +2 min |
| Mon 9 Nov | Sion 05:22 | +1 min | +1 min |
| Sun 8 Nov | Sion 05:19 | 0 min | — |
| Sat 7 Nov | Sion 05:19 | 0 min | — |
| Fri 6 Nov | Sion 05:19 | 0 min | — |
| Thu 5 Nov | Sion 05:22 | +2 min | +2 min |
| Wed 4 Nov | Sion 05:19 | 0 min | — |
| Tue 3 Nov | Sion 05:23 | +3 min | +3 min |
| Mon 2 Nov | Sion 05:19 | 0 min | — |
| Sun 1 Nov | Sion 05:20 | 0 min | — |
| Sat 31 Oct | Sion 05:21 | +1 min | — |
| Fri 30 Oct | Sion 05:20 | 0 min | — |
| Thu 29 Oct | Sion 05:23 | +3 min | +3 min |
| Wed 28 Oct | Sion 05:23 | +2 min | +2 min |
| Tue 27 Oct | Sion 05:19 | −1 min | — |
| Mon 26 Oct | Sion 05:20 | 0 min | — |
| Sun 25 Oct | Sion 05:24 | +5 min | +5 min |
| Sat 24 Oct | Sion 05:24 | +4 min | +4 min |
| Fri 23 Oct | Sion 05:21 | +1 min | +1 min |