R91 6101 Sion – Brig

View line R91

Sion 05:12 → Brig 05:56 Daily 0 h 44 min · 10 stops Regionalps

✓ Today’s run finished

Today it reached Brig at 05:56 0 min

  1. Sion05:12
  2. Sierre/Siders05:22
  3. Salgesch05:26
  4. Turtmann05:34
  5. Gampel-Steg05:37
  6. Visp05:45
  7. Brig05:56

Next service: tomorrow 05:12 from Sion · Fri 6 Nov

Next departure 05:12 tomorrow · Sion
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
92%
33/36 runs under 3 min
RT coverage: 36 full · 0 partial · 5 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Worst days

  • Wed 21 Oct Max en route +7 min · last fix heading to Brig +7 min
  • Sat 17 Oct Max en route +5 min · last fix heading to Brig +5 min
  • Sat 19 Sept Max en route +4 min · last fix heading to Châteauneuf-Conthey +4 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 86% · 31
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 80% W n=5
  • 100% T n=6
  • 100% F n=4
  • 50% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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:12on time on time
05:16≈ on time ≈ on time
05:22 / 05:23≈ on time ≈ +1 min
05:26≈ on time ≈ +1 min
05:30 / 05:31≈ on time ≈ +1 min
05:34≈ on time ≈ +1 min
05:37≈ on time ≈ +1 min
05:40≈ on time ≈ +1 min
05:45 / 05:49≈ on time ≈ +2 min
05:56+1 min +2 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
Thu 5 NovBrig 05:570 min—
Wed 4 NovBrig 05:57No data—
Tue 3 NovBrig 05:58+1 min—
Mon 2 NovBrig 05:59+1 min+1 min
Sun 1 NovNyon 06:30+1 min+3 min
Sat 31 OctNyon 06:29+1 min+3 min
Fri 30 OctBrig 05:58+1 min—
Thu 29 OctBrig 05:59+2 min+2 min
Wed 28 OctBrig 05:59+2 min+2 min
Tue 27 OctBrig 05:570 min—
Mon 26 OctBrig 05:57No data—
Sun 25 OctBrig 05:57+1 min—
Sat 24 OctBrig 05:57No data—
Fri 23 OctBrig 05:59+2 min+2 min
Thu 22 OctBrig 05:58+1 min—
Wed 21 OctBrig 06:04+7 min+7 min
Tue 20 OctBrig 05:58+1 min+1 min
Mon 19 OctBrig 05:57No data—
Sun 18 OctBrig 05:58+1 min—
Sat 17 OctBrig 06:02+5 min+5 min
Fri 16 OctBrig 05:59+2 min+2 min
Thu 15 OctBrig 05:570 min—
Wed 14 OctBrig 05:580 min—
Tue 13 OctBrig 05:59+2 min+2 min
Mon 12 OctBrig 05:58+2 min+2 min
Sun 11 OctNyon 06:290 min—
Sat 10 OctNyon 06:300 min—
Fri 9 OctBrig 05:58+1 min+1 min
Thu 8 OctBrig 05:59+2 min+2 min
Wed 7 OctBrig 05:58+1 min+1 min