S5 15517 Kerzers – Bern

View line S5

Kerzers 05:28 → Bern 05:52 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 7 stops BLS

✓ Today’s run finished

Today it reached Bern at 05:52 0 min

  1. Kerzers05:28
  2. Gümmenen05:32
  3. Rosshäusern05:37
  4. Bern Riedbach05:40
  5. Bern Brünnen Westside05:43
  6. Bern Bümpliz Nord05:46
  7. Bern05:52

Next service: Monday 05:28 from Kerzers · Mon 9 Nov

Next departure 05:28 Monday · Kerzers
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 35 full · 0 partial · 2 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

  • Wed 28 Oct Max en route +7 min · last fix heading to Bern +6 min
  • Thu 13 Aug Max en route +6 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 89% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 86% W n=7
  • 80% T n=5
  • 100% F n=6
  • 100% S n=1
  • 100% S n=2

Stops and timetable

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

Last 90 days, 35 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
05:28on time +1 min
05:32≈ on time ≈ on time
05:37≈ on time ≈ on time
05:40≈ on time ≈ +1 min
05:43 / 05:44≈ on time ≈ +1 min
05:46≈ on time ≈ +1 min
05: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
Fri 6 NovBern 05:530 min—
Thu 5 NovBern 05:490 min—
Wed 4 NovBern 05:52−1 min—
Tue 3 NovBern 05:54+1 min+1 min
Mon 2 NovBern 05:530 min—
Fri 30 OctBern 05:52−1 min—
Thu 29 OctBern 05:530 min—
Wed 28 OctBern 05:59+6 min+7 min
Tue 27 OctBern 05:520 min—
Mon 26 OctBern 05:530 min—
Fri 23 OctBern 05:54+1 min—
Thu 22 OctBern 05:52−1 min—
Wed 21 OctBern 05:54+1 min—
Tue 20 OctBern 05:52−1 min—
Mon 19 OctBern 05:54+1 min+1 min
Fri 16 OctBern 05:520 min—
Thu 15 OctBern 05:53No data—
Wed 14 OctBern 05:530 min—
Tue 13 OctBern 05:520 min—
Mon 12 OctBern 05:52−1 min—
Fri 9 OctBern 05:52−1 min—
Thu 8 OctBern 05:52−1 min—
Wed 7 OctBern 05:530 min—
Tue 6 OctBern 05:53−1 min—
Mon 5 OctBern 05:540 min—
Tue 29 SeptBern 01:010 min—
Mon 28 SeptBern 01:020 min+2 min
Sun 27 SeptBern 01:01+2 min+2 min
Tue 1 SeptBern 01:01+1 min+2 min
Wed 26 AugBern 01:010 min+1 min