RE1 4275 Spiez – Brig

View line RE1

Spiez 15:12 → Brig 16:22 Daily 1 h 10 min · 11 stops BLS

✓ Today’s run finished

Today it reached Brig at 16:22 −5 min

  1. Spiez15:12
  2. Reichenbach im Kandertal15:19
  3. Frutigen15:24
  4. Goppenstein15:52
  5. Ausserberg16:04
  6. Eggerberg16:07
  7. Brig16:22

Next service: tomorrow 15:12 from Spiez · Sun 15 Nov

Next departure 15:12 tomorrow · Spiez
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
52/52 runs under 3 min
RT coverage: 52 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 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

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

  • Early 29% · 15
  • On time 71% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
15:12on time on time
15:17≈ on time ≈ on time
15:19≈ on time ≈ on time
15:24 / 15:25≈ on time ≈ on time
15:40 / 15:41≈ on time ≈ on time
15:52≈ on time ≈ on time
15:56≈ on time ≈ on time
16:04≈ on time ≈ on time
16:07≈ on time ≈ on time
16:10≈ on time ≈ on time
16:221 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:18−5 min—
Fri 13 NovMenziken 00:340 min—
Thu 12 NovMenziken 00:33−2 min+2 min
Wed 11 NovMenziken 00:330 min—
Tue 10 NovMenziken 00:340 min—
Mon 9 NovBrig 16:17−6 min—
Sun 8 NovBrig 16:19−3 min—
Sat 7 NovMenziken 00:340 min—
Fri 6 NovMenziken 00:340 min—
Thu 5 NovMenziken 00:33−1 min—
Wed 4 NovMenziken 00:33−1 min—
Tue 3 NovMenziken 00:340 min—
Mon 2 NovMenziken 00:340 min—
Sun 1 NovBrig 16:200 min—
Sat 31 OctMenziken 00:340 min—
Fri 30 OctMenziken 00:340 min—
Thu 29 OctMenziken 00:340 min—
Wed 28 OctMenziken 00:340 min—
Tue 27 OctMenziken 00:33−1 min—
Mon 26 OctMenziken 00:34−1 min—
Sun 25 OctBrig 16:19−5 min—
Sat 24 OctMenziken 00:330 min—
Fri 23 OctMenziken 00:33−1 min—
Thu 22 OctMenziken 00:340 min—
Wed 21 OctMenziken 00:33−1 min—
Tue 20 OctMenziken 00:33−1 min—
Mon 19 OctMenziken 00:33−1 min—
Sun 18 OctBrig 16:17−6 min—
Sat 17 OctMenziken 00:33−1 min—
Fri 16 OctMenziken 00:340 min—