S5 15576 Bern – Kerzers

View line S5

Bern 20:08 → Kerzers 20:30 Daily 0 h 22 min · 6 stops BLS

Running now · updated 20:31

Between Gümmenen and Kerzers +1 min

Estimated arrival at Kerzers 20:31 20:30 · 8 km/h

  1. Bern20:08
  2. Bern Bümpliz Nord20:12
  3. Bern Brünnen Westside20:14
  4. Rosshäusern20:19
  5. Gümmenen20:24
  6. Kerzers20:30

Today it is running worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

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%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 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 Kerzers, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 30 Oct Max en route +17 min · last fix heading to Kerzers +17 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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 10Today
20:08on time on timePassed
20:12≈ on time ≈ on timePassed
20:14≈ on time ≈ on timePassed
20:19≈ on time ≈ on timePassed
20:24≈ on time ≈ +1 minPassed
20:30on time +1 minNext

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
Sat 7 NovKerzers 20:290 min—
Fri 6 NovKerzers 20:310 min—
Thu 5 NovKerzers 20:29−1 min—
Wed 4 NovKerzers 20:29−1 min—
Tue 3 NovKerzers 20:32+1 min+1 min
Mon 2 NovKerzers 20:290 min—
Sun 1 NovKerzers 20:29−1 min—
Sat 31 OctKerzers 20:310 min—
Fri 30 OctKerzers 20:48+17 min+17 min
Thu 29 OctKerzers 20:30−1 min—
Wed 28 OctKerzers 20:32+1 min—
Tue 27 OctKerzers 20:310 min—
Mon 26 OctKerzers 20:31−1 min—
Sun 25 OctKerzers 20:30−1 min—
Sat 24 OctKerzers 20:30−1 min—
Fri 23 OctKerzers 20:32+1 min—
Thu 22 OctKerzers 20:32+1 min—
Wed 21 OctKerzers 20:310 min—
Tue 20 OctKerzers 20:32+1 min—
Mon 19 OctKerzers 20:31−1 min—
Sun 18 OctKerzers 20:30−1 min—
Sat 17 OctKerzers 20:32+1 min—
Fri 16 OctKerzers 20:320 min—
Thu 15 OctKerzers 20:31+1 min—
Wed 14 OctKerzers 20:32+1 min—
Tue 13 OctKerzers 20:30−1 min—
Mon 12 OctKerzers 20:30−1 min+2 min
Sun 11 OctKerzers 20:310 min—
Sat 10 OctKerzers 20:320 min—
Fri 9 OctKerzers 20:310 min—