R91 6115 St-Gingolph (Suisse) → Brig

View line R91

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

R91 6115 St-Gingolph (Suisse)–Brig: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: −2 min. TrainsRadar data as of 22 Nov 2026, 13:51 (GMT+1).

✓ Today’s run finished

Today it reached Brig at 12:56 −4 min

  1. St-Gingolph (Suisse)10:51
  2. Collombey11:13
  3. Evionnaz11:40
  4. Riddes11:57
  5. Sion12:11
  6. Turtmann12:33
  7. Brig12:56

Next service: tomorrow 10:51 from St-Gingolph (Suisse) · Mon 23 Nov

Next departure 10:51 tomorrow · St-Gingolph (Suisse)
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 5 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

Distribution · 90 days

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

  • Early 62% · 36
  • On time 38% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 58 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
10:51on time on time
10:55 / 11:00≈ on time ≈ on time
11:03≈ on time ≈ on time
11:06≈ on time ≈ on time
11:09≈ on time ≈ on time
11:13≈ on time ≈ on time
11:16≈ on time ≈ on time
11:19≈ on time ≈ on time
11:24 / 11:34≈ on time ≈ on time
11:40≈ 1 min early ≈ on time
11:43≈ 1 min early ≈ on time
11:47≈ 1 min early ≈ on time
11:51≈ 1 min early ≈ on time
11:54≈ 1 min early ≈ on time
11:57 / 11:58≈ 1 min early ≈ on time
12:01≈ 1 min early ≈ on time
12:04≈ 1 min early ≈ on time
12:06≈ 1 min early ≈ on time
12:11≈ 1 min early ≈ on time
12:16≈ 1 min early ≈ on time
12:22≈ 1 min early ≈ on time
12:25≈ 1 min early ≈ on time
12:30≈ 1 min early ≈ on time
12:33≈ 1 min early ≈ on time
12:36 / 12:37≈ 1 min early ≈ on time
12:40≈ 2 min early ≈ on time
12:45 / 12:46≈ 2 min early ≈ on time
12: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
Sun 22 NovBrig 12:54−4 min—
Sat 21 NovBrig 12:53−4 min—
Fri 20 NovBrig 12:54−2 min—
Thu 19 NovBrig 12:57No data—
Wed 18 NovBrig 12:54−3 min—
Tue 17 NovBrig 12:55−3 min—
Mon 16 NovBrig 12:570 min—
Sun 15 NovBrig 12:53−4 min—
Sat 14 NovBrig 12:58+1 min+1 min
Fri 13 NovBrig 12:54−3 min—
Thu 12 NovBrig 12:570 min—
Wed 11 NovBrig 12:54−3 min—
Tue 10 NovBrig 12:54−3 min—
Mon 9 NovBrig 12:570 min—
Sun 8 NovBrig 12:54−3 min—
Sat 7 NovBrig 12:53−4 min—
Fri 6 NovBrig 12:540 min—
Thu 5 NovBrig 12:570 min—
Wed 4 NovBrig 12:540 min—
Tue 3 NovBrig 12:540 min—
Mon 2 NovBrig 12:570 min—
Sun 1 NovBrig 12:53−4 min—
Sat 31 OctBrig 12:53−4 min—
Fri 30 OctBrig 12:55−2 min—
Thu 29 OctBrig 12:57No data—
Wed 28 OctBrig 12:53−4 min—
Tue 27 OctBrig 12:56−2 min—
Mon 26 OctBrig 12:570 min—
Sun 25 OctBrig 12:55−2 min—
Sat 24 OctBrig 12:53−4 min—