R91 6123 St-Gingolph (Suisse) – Brig

View line R91

St-Gingolph (Suisse) 14:51 → Brig 16:56 Daily 2 h 05 min · 28 stops Regionalps

✓ Today’s run finished

Today it reached Brig at 16:56 0 min

  1. St-Gingolph (Suisse)14:51
  2. Collombey15:13
  3. Evionnaz15:40
  4. Riddes15:57
  5. Sion16:11
  6. Turtmann16:33
  7. Brig16:56

Next service: tomorrow 14:51 from St-Gingolph (Suisse) · Sun 15 Nov

Next departure 14: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
96%
50/52 runs under 3 min
RT coverage: 52 full · 0 partial · 0 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −2 min
P90
0min
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 2 Sept Max en route +9 min · last fix heading to Visp +9 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Brig +5 min

Distribution · 90 days

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

  • Early 65% · 34
  • On time 31% · 16
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 86% W n=7
  • 100% T n=9
  • 89% F n=9
  • 100% S n=8
  • 100% S n=6

Stops and timetable

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

Last 90 days, 52 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
14:51on time on time
14:55 / 15:00≈ on time ≈ on time
15:03≈ on time ≈ on time
15:06≈ on time ≈ on time
15:09≈ on time ≈ on time
15:13≈ on time ≈ on time
15:16≈ on time ≈ on time
15:19≈ on time ≈ on time
15:24 / 15:34≈ 1 min early ≈ on time
15:40≈ 1 min early ≈ on time
15:43≈ 1 min early ≈ on time
15:47≈ 1 min early ≈ on time
15:51≈ 1 min early ≈ on time
15:54≈ 1 min early ≈ on time
15:57 / 15:58≈ 1 min early ≈ on time
16:01≈ 1 min early ≈ on time
16:04≈ 1 min early ≈ on time
16:06≈ 1 min early ≈ on time
16:11≈ 1 min early ≈ on time
16:16≈ 1 min early ≈ on time
16:22≈ 1 min early ≈ on time
16:25≈ 1 min early ≈ on time
16:30≈ 2 min early ≈ on time
16:33≈ 2 min early ≈ on time
16:36 / 16:37≈ 2 min early ≈ on time
16:40≈ 2 min early ≈ on time
16:45 / 16:46≈ 2 min early ≈ on time
16:562 min early on time

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
Sat 14 NovBrig 16:540 min—
Fri 13 NovBrig 16:53−4 min—
Thu 12 NovBrig 16:54−1 min—
Wed 11 NovBrig 16:53−4 min—
Tue 10 NovBrig 16:54−1 min—
Mon 9 NovBrig 16:540 min—
Sun 8 NovBrig 16:54−2 min—
Sat 7 NovBrig 16:53−3 min—
Fri 6 NovBrig 16:58+1 min+1 min
Thu 5 NovBrig 16:54−2 min—
Wed 4 NovBrig 16:54−3 min—
Tue 3 NovBrig 16:53−4 min—
Mon 2 NovBrig 16:54−1 min—
Sun 1 NovBrig 16:54−3 min—
Sat 31 OctBrig 16:54−3 min—
Fri 30 OctBrig 16:55−2 min—
Thu 29 OctBrig 16:54−3 min—
Wed 28 OctBrig 16:56−1 min—
Tue 27 OctBrig 16:53−4 min—
Mon 26 OctBrig 16:55−2 min—
Sun 25 OctBrig 16:55−2 min—
Sat 24 OctBrig 16:56−1 min—
Fri 23 OctBrig 17:01+5 min+5 min
Thu 22 OctBrig 16:55−2 min—
Wed 21 OctBrig 16:53−4 min—
Tue 20 OctBrig 16:55−2 min—
Mon 19 OctBrig 16:570 min—
Sun 18 OctBrig 16:56−1 min—
Sat 17 OctBrig 16:55−2 min—
Fri 16 OctBrig 16:55−3 min—