S5 15561 Kerzers – Bern

View line S5

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

It has not run yet today

Last recorded run: Wednesday 11 November +2 min

Next service: today 16:30 from Kerzers · Thu 12 Nov

Next departure 16:30 today · Kerzers
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 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 Bern, 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 22 Oct Max en route +5 min · last fix heading to Bern +5 min

Distribution · 90 days

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

  • Early 7% · 3
  • On time 91% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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:30on time on time
16:35≈ on time ≈ on time
16:39≈ on time ≈ +1 min
16:44≈ on time ≈ +1 min
16:46≈ on time ≈ +1 min
16:52on 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
Wed 11 NovBern 16:54+2 min+2 min
Tue 10 NovBern 16:530 min—
Mon 9 NovBern 16:52−1 min—
Sun 8 NovBern 16:54+1 min—
Sat 7 NovBern 16:520 min—
Fri 6 NovBern 16:52−1 min—
Thu 5 NovBern 16:530 min—
Wed 4 NovBern 16:52−1 min—
Tue 3 NovBern 16:530 min—
Mon 2 NovBern 16:54+1 min—
Sun 1 NovBern 16:52−1 min—
Sat 31 OctBern 16:530 min—
Fri 30 OctBern 16:530 min—
Thu 29 OctBern 16:53−1 min—
Wed 28 OctBern 16:55+2 min+2 min
Tue 27 OctBern 16:54+1 min—
Mon 26 OctBern 16:54+1 min—
Sun 25 OctBern 16:520 min—
Sat 24 OctBern 16:520 min—
Fri 23 OctBern 16:530 min—
Thu 22 OctBern 16:58+5 min+5 min
Wed 21 OctBern 16:530 min—
Tue 20 OctBern 16:540 min—
Mon 19 OctBern 16:530 min—
Sun 18 OctBern 16:52−1 min—
Sat 17 OctBern 16:530 min—
Fri 16 OctBern 16:530 min—
Thu 15 OctBern 16:52−1 min—
Wed 14 OctBern 16:52−1 min—
Tue 13 OctBern 16:53−1 min—