RE1 4268 Brig – Spiez

View line RE1

Brig 11:36 → Spiez 12:44 Daily 1 h 08 min · 11 stops BLS

Running now · updated 12:20

Position estimated from the timetable

Between Kandersteg and Frutigen 0 min

Estimated arrival at Spiez 12:44 · 45 km/h

  1. Brig11:36
  2. Eggerberg11:43
  3. Ausserberg11:48
  4. Goppenstein12:01
  5. Kandersteg12:13
  6. Frutigen12:29
  7. Spiez12:44

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 34 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 14% · 5
  • On time 86% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=6
  • 100% W n=7
  • 100% T n=2
  • 100% F n=6
  • 100% S n=5
  • 100% S n=7

Stops and timetable

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

Last 90 days, 35 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 10Today
11:36on time on timePassed
11:40≈ on time ≈ on timePassed
11:43≈ on time ≈ on timePassed
11:48≈ on time ≈ on timePassed
11:54≈ on time ≈ on timePassed
12:01 / 12:02≈ on time ≈ on timePassed
12:13 / 12:14≈ on time ≈ on timePassed
12:29 / 12:30≈ on time ≈ on timeNext
12:34≈ on time ≈ on time
12:35≈ on time ≈ on time
12:44on time 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
Fri 13 NovFrutigen 12:19Partial coverage0 min—
Thu 12 NovSpiez 12:440 min—
Wed 11 NovSpiez 12:440 min—
Tue 10 NovSpiez 12:440 min—
Mon 9 NovSpiez 12:44No data—
Sun 8 NovSpiez 12:47+2 min+2 min
Sat 7 NovSpiez 12:440 min—
Fri 6 NovSpiez 12:44−1 min—
Thu 5 NovSpiez 12:44No data—
Wed 4 NovSpiez 12:44−1 min—
Tue 3 NovSpiez 12:44−2 min—
Mon 2 NovSpiez 12:44No data—
Sun 1 NovSpiez 12:44−1 min—
Sat 31 OctSpiez 12:450 min—
Fri 30 OctSpiez 12:46+1 min—
Thu 29 OctSpiez 12:45No data—
Wed 28 OctSpiez 12:450 min—
Tue 27 OctSpiez 12:450 min—
Mon 26 OctSpiez 12:45No data—
Sun 25 OctSpiez 12:440 min—
Sat 24 OctSpiez 12:450 min—
Fri 23 OctSpiez 12:450 min—
Thu 22 OctSpiez 12:45No data—
Wed 21 OctSpiez 12:44−1 min—
Tue 20 OctSpiez 12:460 min—
Mon 19 OctSpiez 12:45No data—
Sun 18 OctSpiez 12:45−1 min—
Sat 17 OctSpiez 12:44−1 min—
Fri 16 OctSpiez 12:450 min—
Thu 15 OctSpiez 12:45No data—