RE1 4164 Spiez – Bern

View line RE1

Spiez 10:50 → Bern 11:22 Daily 0 h 32 min · 4 stops BLS

✓ Today’s run finished

Today it reached Bern at 11:22 0 min

  1. Spiez10:50
  2. Thun10:58
  3. Münsingen11:08
  4. Bern11:22

Next service: tomorrow 10:50 from Spiez · Fri 6 Nov

Next departure 10:50 tomorrow · Spiez
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
49/51 runs under 3 min
RT coverage: 51 full · 0 partial · 1 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 Bern, 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 8 Oct Max en route +6 min · last fix heading to Aarau +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Aarau +5 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 94% · 48
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 51 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
10:50on time on time
10:58 / 10:59≈ on time ≈ on time
11:08≈ on time ≈ +1 min
11:22+1 min +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
Thu 5 NovBern 11:230 min—
Wed 4 NovAarau 20:19+1 min—
Tue 3 NovAarau 20:19+1 min+4 min
Mon 2 NovAarau 20:19+1 min+2 min
Sun 1 NovAarau 20:19−1 min—
Sat 31 OctAarau 20:20+1 min+1 min
Fri 30 OctAarau 20:22+2 min+4 min
Thu 29 OctAarau 20:21+1 min+2 min
Wed 28 OctAarau 20:21+1 min+1 min
Tue 27 OctAarau 20:20−1 min+2 min
Mon 26 OctAarau 20:200 min—
Sun 25 OctAarau 20:20+1 min—
Sat 24 OctAarau 20:200 min—
Fri 23 OctAarau 20:25+5 min+5 min
Thu 22 OctAarau 20:21+1 min+2 min
Wed 21 OctAarau 20:21+1 min+2 min
Tue 20 OctAarau 20:210 min—
Mon 19 OctAarau 20:190 min+3 min
Sun 18 OctAarau 20:200 min—
Sat 17 OctAarau 20:21+1 min+2 min
Fri 16 OctAarau 20:210 min+2 min
Thu 15 OctAarau 20:200 min+1 min
Wed 14 OctAarau 20:19−1 min—
Tue 13 OctAarau 20:21+1 min+11 min
Mon 12 OctAarau 20:20+1 min—
Sun 11 OctAarau 20:21+1 min+2 min
Sat 10 OctAarau 20:200 min+1 min
Fri 9 OctAarau 20:200 min+1 min
Thu 8 OctAarau 20:26+6 min+6 min
Wed 7 OctAarau 20:210 min+1 min