S5 15589 Kerzers – Bern

View line S5

Kerzers 23:30 → Bern 23:54 Daily 0 h 24 min · 6 stops BLS

It has not run yet today

Last recorded run: Sunday 15 November −1 min

Next service: today 23:30 from Kerzers · Mon 16 Nov

Next departure 23:30 today · Kerzers
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
67/67 runs under 3 min
RT coverage: 67 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 24% · 16
  • On time 76% · 51
  • 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=8
  • 100% T n=9
  • 100% F n=9
  • 100% S n=11
  • 100% S n=10

Stops and timetable

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

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