R91 6131 St-Gingolph (Suisse) – Brig

View line R91

St-Gingolph (Suisse) 18:51 → Brig 20:56 Daily 2 h 05 min · 26 stops Regionalps

✓ Today’s run finished

Today it reached Brig at 20:56 −1 min

  1. St-Gingolph (Suisse)18:51
  2. Vionnaz19:09
  3. St-Maurice19:23
  4. Saxon19:46
  5. St-Léonard20:17
  6. Turtmann20:35
  7. Brig20:56

Next service: tomorrow 18:51 from St-Gingolph (Suisse) · Sat 7 Nov

Next departure 18:51 tomorrow · St-Gingolph (Suisse)
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
60/63 runs under 3 min
RT coverage: 63 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −2 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

Worst days

  • Wed 4 Nov Max en route +10 min · last fix heading to Brig +10 min
  • Sat 26 Sept Max en route +4 min · last fix heading to Walzenhausen +4 min
  • Mon 21 Sept Max en route +4 min · last fix heading to Walzenhausen +4 min

Distribution · 90 days

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

  • Early 43% · 27
  • On time 52% · 33
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=8
  • 86% W n=7
  • 100% T n=10
  • 100% F n=10
  • 89% S n=9
  • 100% S n=11

Stops and timetable

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

Last 90 days, 63 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
18:51on time on time
18:55 / 19:00≈ on time ≈ on time
19:03≈ on time ≈ on time
19:06≈ on time ≈ on time
19:09≈ on time ≈ on time
19:13≈ on time ≈ on time
19:16≈ on time ≈ on time
19:19≈ on time ≈ on time
19:23 / 19:25≈ on time ≈ on time
19:29≈ on time ≈ +1 min
19:33≈ on time ≈ +1 min
19:37≈ on time ≈ +1 min
19:41≈ on time ≈ +1 min
19:46 / 19:50≈ on time ≈ +1 min
19:54≈ on time ≈ +1 min
20:00≈ on time ≈ +1 min
20:04 / 20:13≈ on time ≈ +1 min
20:17≈ on time ≈ +1 min
20:23≈ on time ≈ +1 min
20:27≈ on time ≈ +1 min
20:31≈ on time ≈ +1 min
20:35≈ on time ≈ +1 min
20:38≈ on time ≈ +1 min
20:42≈ on time ≈ +1 min
20:46 / 20:47≈ on time ≈ +1 min
20:56on 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
Fri 6 NovBrig 20:54−1 min—
Thu 5 NovBrig 20:54−2 min—
Wed 4 NovBrig 21:07+10 min+10 min
Tue 3 NovBrig 20:54−2 min—
Mon 2 NovBrig 20:54−1 min—
Sun 1 NovBrig 20:54−1 min—
Sat 31 OctBrig 20:54−2 min—
Fri 30 OctBrig 20:56−1 min—
Thu 29 OctBrig 20:55−2 min—
Wed 28 OctBrig 20:55−2 min—
Tue 27 OctBrig 20:55−2 min—
Mon 26 OctBrig 20:570 min—
Sun 25 OctBrig 20:55−1 min—
Sat 24 OctBrig 20:54−2 min—
Fri 23 OctBrig 20:55−2 min—
Thu 22 OctBrig 20:54−3 min—
Wed 21 OctBrig 20:54−2 min—
Tue 20 OctBrig 20:570 min—
Mon 19 OctBrig 20:54−2 min—
Sun 18 OctBrig 20:55−2 min—
Sat 17 OctBrig 20:55−1 min—
Fri 16 OctBrig 20:56−2 min—
Thu 15 OctBrig 20:55−2 min—
Wed 14 OctBrig 20:55−2 min—
Tue 13 OctBrig 20:55−2 min—
Mon 12 OctBrig 20:54−3 min—
Sun 11 OctBrig 20:58+1 min—
Sat 10 OctBrig 20:56−1 min—
Fri 9 OctBrig 20:57−1 min—
Thu 8 OctBrig 20:55−3 min—