S52 16291 Kerzers – Bern

View line S52

Kerzers 00:04 → Bern 00:30 Daily 0 h 26 min · 7 stops BLS

✓ Today’s run finished

Today it reached Bern at 00:30 0 min

  1. Kerzers00:04
  2. Gümmenen00:08
  3. Rosshäusern00:14
  4. Bern Riedbach00:16
  5. Bern Brünnen Westside00:20
  6. Bern Bümpliz Nord00:23
  7. Bern00:30

Next service: tomorrow 00:04 from Kerzers · Sun 8 Nov

Next departure 00:04 tomorrow · Kerzers
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
63/66 runs under 3 min
RT coverage: 66 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: +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

  • Tue 13 Oct Max en route +5 min · last fix heading to Bern +5 min
  • Thu 20 Aug Max en route +3 min · last fix heading to Kerzers +3 min
  • Sat 29 Aug Max en route +3 min · last fix heading to Kerzers +3 min

Distribution · 90 days

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

  • Early 39% · 26
  • On time 56% · 37
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 88% T n=8
  • 100% W n=9
  • 89% T n=9
  • 100% F n=10
  • 92% S n=12
  • 100% S n=9

Stops and timetable

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

Last 90 days, 66 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
00:04on time on time
00:08 / 00:09≈ on time ≈ on time
00:14≈ on time ≈ +1 min
00:16≈ on time ≈ on time
00:20 / 00:21≈ on time ≈ +1 min
00:23≈ on time ≈ +1 min
00:301 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
Sat 7 NovBern 00:290 min+1 min
Fri 6 NovBern 00:290 min—
Thu 5 NovBern 00:29−2 min—
Wed 4 NovBern 00:29−1 min—
Tue 3 NovBern 00:29−1 min—
Mon 2 NovBern 00:29−1 min—
Sun 1 NovBern 00:29−2 min—
Sat 31 OctBern 00:30−1 min—
Fri 30 OctBern 00:29−2 min—
Thu 29 OctBern 00:30−1 min—
Wed 28 OctBern 00:30−2 min—
Tue 27 OctBern 00:29−2 min—
Mon 26 OctBern 00:30−1 min—
Sun 25 OctBern 00:30−1 min—
Sat 24 OctBern 00:32+1 min+1 min
Fri 23 OctBern 00:310 min—
Thu 22 OctBern 00:29−2 min—
Wed 21 OctBern 00:30−1 min—
Tue 20 OctBern 00:29−2 min—
Mon 19 OctBern 00:32+1 min—
Sun 18 OctBern 00:30−1 min—
Sat 17 OctBern 00:29−2 min—
Fri 16 OctBern 00:29−1 min—
Thu 15 OctBern 00:33+1 min+2 min
Wed 14 OctBern 00:29−2 min—
Tue 13 OctBern 00:36+5 min+5 min
Mon 12 OctBern 00:29−2 min—
Sun 11 OctBern 00:310 min—
Sat 10 OctBern 00:310 min—
Fri 9 OctBern 00:29−2 min—