S5 15536 Bern – Kerzers

View line S5

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

✓ Today’s run finished

Today it reached Kerzers at 10:30 0 min

  1. Bern10:08
  2. Bern Bümpliz Nord10:12
  3. Bern Brünnen Westside10:14
  4. Rosshäusern10:19
  5. Gümmenen10:24
  6. Kerzers10:30

Next service: tomorrow 10:08 from Bern · Thu 19 Nov

Next departure 10:08 tomorrow · Bern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
45/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 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

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

  • Early 2% · 1
  • On time 98% · 44
  • 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=7
  • 100% W n=7
  • 100% T n=5
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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