S5 15540 Bern – Kerzers

View line S5

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

✓ Today’s run finished

Today it reached Kerzers at 11:30 0 min

  1. Bern11:08
  2. Bern Bümpliz Nord11:12
  3. Bern Brünnen Westside11:14
  4. Rosshäusern11:19
  5. Gümmenen11:24
  6. Kerzers11:30

Next service: tomorrow 11:08 from Bern · Sat 7 Nov

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

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

  • Early 0% · 0
  • On time 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
11:08on time on time
11:12≈ on time ≈ on time
11:14≈ on time ≈ on time
11:19≈ on time ≈ on time
11:24≈ on time ≈ on time
11:30on time on time

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