RE1 4264 Brig – Spiez

View line RE1

Brig 22:07 → Spiez 23:18 Daily 1 h 11 min · 11 stops BLS

✓ Today’s run finished

Today it reached Spiez at 23:18 0 min

  1. Brig22:07
  2. Eggerberg22:14
  3. Ausserberg22:19
  4. Goppenstein22:32
  5. Frutigen23:00
  6. Reichenbach im Kandertal23:09
  7. Spiez23:18

Next service: tomorrow 22:07 from Brig · Fri 13 Nov

Next departure 22:07 tomorrow · Brig
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 54 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Spiez, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 17 Aug Max en route +8 min · last fix heading to Aarau +8 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Aarau +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Aarau +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 93% · 50
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 54 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
22:07on time on time
22:11≈ on time ≈ on time
22:14≈ on time ≈ on time
22:19≈ on time ≈ on time
22:25≈ on time ≈ on time
22:32 / 22:33≈ on time ≈ on time
22:44 / 22:45≈ on time ≈ on time
23:00 / 23:05≈ on time ≈ +1 min
23:09≈ on time ≈ +1 min
23:11≈ on time ≈ +1 min
23:18on 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
Thu 12 NovSpiez 10:440 min—
Wed 11 NovAarau 20:330 min—
Tue 10 NovAarau 20:33+1 min—
Mon 9 NovAarau 20:32−1 min—
Sun 8 NovSpiez 10:440 min—
Sat 7 NovAarau 20:33+1 min—
Fri 6 NovAarau 20:330 min+1 min
Thu 5 NovAarau 20:290 min—
Wed 4 NovAarau 20:330 min—
Tue 3 NovAarau 20:33−1 min—
Mon 2 NovAarau 20:33−1 min—
Sun 1 NovSpiez 10:450 min—
Sat 31 OctAarau 20:330 min—
Fri 30 OctAarau 20:34+1 min—
Thu 29 OctAarau 20:330 min—
Wed 28 OctAarau 20:330 min—
Tue 27 OctAarau 20:34+1 min—
Mon 26 OctAarau 20:330 min—
Sun 25 OctSpiez 10:440 min—
Sat 24 OctAarau 20:32−1 min—
Fri 23 OctAarau 20:36+3 min+3 min
Thu 22 OctAarau 20:33−1 min—
Wed 21 OctAarau 20:320 min—
Tue 20 OctAarau 20:33−1 min—
Mon 19 OctAarau 20:320 min—
Sun 18 OctSpiez 10:46+1 min—
Sat 17 OctAarau 20:330 min—
Fri 16 OctAarau 20:33−1 min—
Thu 15 OctAarau 20:32−1 min—
Wed 14 OctAarau 20:340 min—