RE1 4174 Spiez – Bern

View line RE1

Spiez 15:50 → Bern 16:22 Daily 0 h 32 min · 4 stops BLS

✓ Today’s run finished

Today it reached Bern at 16:23 +1 min

  1. Spiez15:50
  2. Thun15:58
  3. Münsingen16:08
  4. Bern16:22

Next service: tomorrow 15:50 from Spiez · Wed 18 Nov

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

Distribution · 90 days

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

  • Early 2% · 1
  • On time 98% · 58
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=7
  • 100% T n=9
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

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