RE1 4283 Spiez – Brig

View line RE1

Spiez 19:12 → Brig 20:22 Daily 1 h 10 min · 11 stops BLS

It has not run yet today

Last recorded run: Friday 6 November −5 min

Next service: today 19:12 from Spiez · Sat 7 Nov

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

Worst days

  • Thu 15 Oct Max en route +14 min · last fix heading to Brig +11 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 80% T n=5
  • 100% F n=4
  • 100% S n=4
  • 100% S n=7

Stops and timetable

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

Last 90 days, 32 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
19:12on time on time
19:17≈ on time ≈ on time
19:19≈ 1 min early ≈ on time
19:24 / 19:25≈ 1 min early ≈ on time
19:40 / 19:41≈ 2 min early ≈ 1 min early
19:52≈ 3 min early ≈ 1 min early
19:56≈ 3 min early ≈ 1 min early
20:04≈ 4 min early ≈ 1 min early
20:07≈ 4 min early ≈ 1 min early
20:10≈ 4 min early ≈ 1 min early
20:225 min early 2 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
Fri 6 NovBrig 20:14−5 min—
Thu 5 NovBrig 20:180 min—
Wed 4 NovBrig 20:19−4 min—
Tue 3 NovBrig 20:18−5 min—
Sun 1 NovBrig 20:17−6 min—
Sat 31 OctBrig 20:20−3 min—
Fri 30 OctBrig 20:23No data—
Thu 29 OctBrig 20:18−5 min—
Tue 27 OctBrig 20:19−5 min—
Mon 26 OctBrig 20:18−5 min—
Sun 25 OctBrig 20:17−6 min—
Sat 24 OctBrig 20:19−4 min—
Fri 23 OctBrig 20:25+2 min+5 min
Thu 22 OctBrig 20:21−2 min—
Wed 21 OctBrig 20:17−6 min—
Tue 20 OctBrig 20:17−6 min—
Mon 19 OctBrig 20:18−5 min—
Sun 18 OctBrig 20:23−4 min—
Sat 17 OctBrig 20:17−6 min—
Fri 16 OctBrig 20:19−5 min—
Thu 15 OctBrig 20:34+11 min+14 min
Wed 14 OctBrig 20:19−5 min—
Mon 12 OctBrig 20:17−6 min—
Sun 11 OctBrig 20:17−6 min—
Sat 10 OctBrig 20:18−5 min—
Fri 9 OctBrig 20:20−3 min—
Thu 8 OctBrig 20:18−5 min—
Wed 7 OctBrig 20:18−5 min—
Tue 6 OctBrig 20:17−6 min—
Mon 5 OctBrig 20:17−7 min—