S5 15560 Bern – Kerzers

View line S5

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

✓ Today’s run finished

Today it reached Kerzers at 16:30 −1 min

  1. Bern16:08
  2. Bern Bümpliz Nord16:12
  3. Bern Brünnen Westside16:14
  4. Rosshäusern16:19
  5. Gümmenen16:24
  6. Kerzers16:30

Next service: tomorrow 16:08 from Bern · Tue 10 Nov

Next departure 16:08 tomorrow · Bern
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%
44/44 runs under 3 min
RT coverage: 44 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

Distribution · 90 days

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

  • Early 5% · 2
  • On time 95% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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
16:08on time on time
16:12≈ on time ≈ on time
16:14≈ on time ≈ on time
16:19≈ on time ≈ on time
16:24≈ on time ≈ +1 min
16:30on time +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
Mon 9 NovKerzers 16:29−1 min—
Sun 8 NovKerzers 16:34+2 min+2 min
Sat 7 NovKerzers 16:29−1 min—
Fri 6 NovKerzers 16:290 min—
Thu 5 NovKerzers 16:290 min—
Wed 4 NovKerzers 16:32+1 min—
Tue 3 NovKerzers 16:29−1 min—
Mon 2 NovKerzers 16:29−1 min—
Sun 1 NovKerzers 16:310 min—
Sat 31 OctKerzers 16:310 min—
Fri 30 OctKerzers 16:30−1 min—
Thu 29 OctKerzers 16:310 min—
Wed 28 OctKerzers 16:310 min—
Tue 27 OctKerzers 16:310 min—
Mon 26 OctKerzers 16:310 min—
Sun 25 OctKerzers 16:310 min—
Sat 24 OctKerzers 16:32+1 min—
Fri 23 OctKerzers 16:310 min—
Thu 22 OctKerzers 16:32+1 min—
Wed 21 OctKerzers 16:30−1 min—
Tue 20 OctKerzers 16:310 min—
Mon 19 OctKerzers 16:32+1 min—
Sun 18 OctKerzers 16:310 min—
Sat 17 OctKerzers 16:310 min—
Fri 16 OctKerzers 16:31−1 min—
Thu 15 OctKerzers 16:30−1 min—
Wed 14 OctKerzers 16:31+1 min—
Tue 13 OctKerzers 16:310 min—
Mon 12 OctKerzers 16:30−1 min—
Sun 11 OctKerzers 16:30−1 min—