RE1 4267 Spiez – Brig

View line RE1

Spiez 11:12 → Brig 12:22 Daily 1 h 10 min · 11 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November −5 min

Next service: today 11:12 from Spiez · Thu 5 Nov

Next departure 11:12 today · Spiez
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 10 no data
Typical delay
−5min
Median at arrival, 90 days
30 days: −5 min
P90
−1min
9 in 10 runs arrive with less than this
30 days: −2 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

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

  • Early 87% · 33
  • On time 13% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
11:12on time on time
11:17≈ on time ≈ on time
11:19≈ on time ≈ on time
11:24 / 11:25≈ 1 min early ≈ on time
11:40 / 11:41≈ 2 min early ≈ on time
11:52≈ 3 min early ≈ on time
11:56≈ 3 min early ≈ on time
12:04≈ 3 min early ≈ on time
12:07≈ 4 min early ≈ on time
12:10≈ 4 min early ≈ 1 min early
12:225 min early 1 min early

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 4 NovBrig 12:18−5 min—
Tue 3 NovBrig 12:19−1 min—
Mon 2 NovBrig 12:23No data—
Sun 1 NovBrig 12:22−1 min—
Sat 31 OctBrig 12:19−4 min—
Fri 30 OctBrig 12:21−2 min—
Thu 29 OctBrig 12:23No data—
Wed 28 OctBrig 12:19−5 min—
Tue 27 OctBrig 12:17−6 min—
Mon 26 OctBrig 12:24No data—
Sun 25 OctBrig 12:19−4 min—
Sat 24 OctBrig 12:20−3 min—
Fri 23 OctBrig 12:17−5 min—
Thu 22 OctBrig 12:23No data—
Wed 21 OctBrig 12:17−6 min—
Tue 20 OctBrig 12:18−6 min—
Mon 19 OctBrig 12:23No data—
Sun 18 OctBrig 12:18−5 min—
Sat 17 OctBrig 12:17−6 min—
Fri 16 OctBrig 12:19−5 min—
Thu 15 OctBrig 12:23No data—
Wed 14 OctBrig 12:18−5 min—
Tue 13 OctBrig 12:19−5 min—
Mon 12 OctBrig 12:23No data—
Sun 11 OctBrig 12:18−5 min—
Sat 10 OctBrig 12:18−5 min—
Fri 9 OctBrig 12:18−5 min—
Thu 8 OctBrig 12:18−5 min—
Wed 7 OctBrig 12:17−5 min—
Tue 6 OctBrig 12:20−3 min—