RE1 4161 Bern → Spiez

View line RE1

Bern 07:39 → Spiez 08:10 Daily 0 h 31 min · 4 stops BLS

RE1 4161 Bern–Spiez: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 08:24 (GMT+1).

✓ Today’s run finished

Today it reached Spiez at 08:10 0 min

  1. Bern07:39
  2. Münsingen07:51
  3. Thun08:00
  4. Spiez08:10

Next service: tomorrow 07:39 from Bern · Mon 23 Nov

Next departure 07:39 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
68/70 runs under 3 min
RT coverage: 70 full · 0 partial · 2 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

  • Sun 1 Nov Max en route +10 min · last fix heading to Menziken +10 min
  • Thu 8 Oct Max en route +8 min · last fix heading to Menziken +8 min

Distribution · 90 days

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

  • Early 13% · 9
  • On time 84% · 59
  • 3–10 min 1% · 1
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=11
  • 90% T n=10
  • 100% F n=10
  • 100% S n=9
  • 91% S n=11

Stops and timetable

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

Last 90 days, 70 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
07:39on time on time
07:51≈ on time ≈ on time
08:00 / 08:01≈ on time ≈ +1 min
08:10on 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
Sun 22 NovSpiez 08:100 min—
Sat 21 NovMenziken 21:19+1 min+1 min
Fri 20 NovMenziken 21:180 min—
Thu 19 NovMenziken 21:18−1 min—
Wed 18 NovMenziken 21:190 min—
Tue 17 NovMenziken 21:190 min—
Mon 16 NovMenziken 21:190 min—
Sun 15 NovMenziken 21:19+1 min—
Sat 14 NovMenziken 21:180 min—
Fri 13 NovMenziken 21:190 min—
Thu 12 NovMenziken 21:19−1 min+2 min
Wed 11 NovMenziken 21:190 min—
Tue 10 NovMenziken 21:18−1 min—
Mon 9 NovMenziken 21:190 min—
Sun 8 NovMenziken 21:190 min—
Sat 7 NovMenziken 21:190 min+2 min
Fri 6 NovMenziken 21:19+1 min—
Thu 5 NovMenziken 21:180 min—
Wed 4 NovMenziken 21:19+1 min—
Tue 3 NovMenziken 21:190 min—
Mon 2 NovMenziken 21:190 min—
Sun 1 NovMenziken 21:29+10 min+10 min
Sat 31 OctMenziken 21:190 min—
Fri 30 OctMenziken 21:190 min+3 min
Thu 29 OctMenziken 21:190 min—
Wed 28 OctMenziken 21:190 min+3 min
Tue 27 OctMenziken 21:20+1 min+3 min
Mon 26 OctMenziken 21:200 min—
Sun 25 OctMenziken 21:190 min—
Sat 24 OctMenziken 21:180 min—