RE1 4290 Brig – Spiez

View line RE1

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

✓ Today’s run finished

Today it reached Spiez at 23:15 −1 min

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

Next service: tomorrow 22:07 from Brig · Thu 12 Nov

Next departure 22:07 tomorrow · Brig
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 3 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 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

  • Sat 7 Nov Max en route +5 min · last fix heading to Spiez +4 min

Distribution · 90 days

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

  • Early 25% · 12
  • On time 73% · 35
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 48 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:01≈ on time ≈ on time
23:05≈ 1 min early ≈ +1 min
23:06≈ 1 min early ≈ +1 min
23:151 min early +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
Wed 11 NovSpiez 23:14−1 min—
Tue 10 NovSpiez 23:17+1 min—
Mon 9 NovSpiez 23:15−1 min—
Sun 8 NovSpiez 23:14−1 min—
Sat 7 NovSpiez 23:19+4 min+5 min
Fri 6 NovSpiez 23:14−2 min—
Thu 5 NovSpiez 23:14−2 min—
Wed 4 NovSpiez 23:14−2 min—
Tue 3 NovSpiez 23:14No data—
Mon 2 NovSpiez 23:14−1 min+2 min
Sun 1 NovSpiez 23:14No data—
Sat 31 OctSpiez 23:160 min—
Fri 30 OctSpiez 23:160 min—
Thu 29 OctSpiez 23:15−1 min—
Wed 28 OctSpiez 23:160 min—
Tue 27 OctSpiez 23:15−1 min—
Mon 26 OctSpiez 23:15−1 min—
Sun 25 OctSpiez 23:15−1 min—
Sat 24 OctSpiez 23:16+1 min—
Fri 23 OctSpiez 23:18+2 min+2 min
Thu 22 OctSpiez 23:15−1 min—
Wed 21 OctSpiez 23:17+1 min+1 min
Tue 20 OctSpiez 23:15−1 min—
Mon 19 OctSpiez 23:160 min—
Sun 18 OctThun 23:30No data—
Sat 17 OctThun 23:280 min—
Fri 16 OctSpiez 23:16−1 min—
Thu 15 OctSpiez 23:15−1 min—
Wed 14 OctSpiez 23:160 min—
Tue 13 OctSpiez 23:160 min—