S52 16234 Bern – Kerzers

View line S52

Bern 20:34 → Kerzers 21:00 Daily 0 h 26 min · 7 stops BLS

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 20:34 from Bern · Fri 13 Nov

Next departure 20:34 today · Bern
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 2 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

Worst days

  • Mon 12 Oct Max en route +18 min · last fix heading to Kerzers +18 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 38
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 40 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
20:34on time on time
20:39≈ 1 min early ≈ on time
20:42≈ 1 min early ≈ on time
20:45≈ 1 min early ≈ on time
20:48≈ 1 min early ≈ on time
20:53 / 20:54≈ 1 min early ≈ on time
21:001 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
Thu 12 NovKerzers 09:590 min—
Wed 11 NovKerzers 09:59−1 min—
Tue 10 NovKerzers 09:59No data—
Mon 9 NovKerzers 09:590 min—
Sun 8 NovKerzers 09:590 min—
Sat 7 NovKerzers 09:590 min—
Fri 6 NovKerzers 09:590 min—
Thu 5 NovKerzers 09:59−1 min—
Wed 4 NovKerzers 09:590 min—
Tue 3 NovKerzers 09:590 min—
Mon 2 NovKerzers 09:590 min—
Sun 1 NovKerzers 10:00−1 min—
Sat 31 OctKerzers 10:00−1 min—
Fri 30 OctKerzers 10:010 min—
Thu 29 OctKerzers 10:01No data—
Wed 28 OctKerzers 10:01−1 min—
Tue 27 OctKerzers 10:01−1 min—
Mon 26 OctBern 11:01−1 min—
Sun 25 OctKerzers 10:00−1 min—
Sat 24 OctKerzers 10:00−1 min—
Fri 23 OctKerzers 10:00−1 min—
Thu 22 OctKerzers 10:010 min—
Wed 21 OctKerzers 10:00−1 min—
Tue 20 OctKerzers 10:01−1 min—
Mon 19 OctKerzers 10:00−1 min—
Sun 18 OctKerzers 10:00−1 min—
Sat 17 OctKerzers 10:00−1 min—
Fri 16 OctKerzers 10:00−1 min—
Thu 15 OctKerzers 10:00−1 min—
Wed 14 OctKerzers 10:00−1 min—