RE1 4178 Spiez – Bern

View line RE1

Spiez 17:50 → Bern 18:22 Daily 0 h 32 min · 4 stops BLS

✓ Today’s run finished

Today it reached Bern at 18:22 0 min

  1. Spiez17:50
  2. Thun17:58
  3. Münsingen18:08
  4. Bern18:22

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

Next departure 17: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%
64/64 runs under 3 min
RT coverage: 64 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=11
  • 100% T n=10
  • 100% F n=10
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

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