RE1 4183 Bern – Spiez

View line RE1

Bern 18:39 → Spiez 19:10 Daily 0 h 31 min · 4 stops BLS

✓ Today’s run finished

Today it reached Spiez at 19:10 0 min

  1. Bern18:39
  2. Münsingen18:51
  3. Thun19:00
  4. Spiez19:10

Next service: tomorrow 18:39 from Bern · Sat 7 Nov

Next departure 18:39 tomorrow · Bern
On-time · 30 days
87%
26/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
90%
35/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 15 Oct Max en route +21 min · last fix heading to Spiez +21 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Spiez +4 min
  • Mon 2 Nov Max en route +3 min · last fix heading to Spiez +3 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Spiez +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 35
  • 3–10 min 8% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=6
  • 67% T n=6
  • 100% F n=5
  • 83% S n=6
  • 100% S n=6

Stops and timetable

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

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