S52 16250 Bern – Kerzers

View line S52

Bern 13:34 → Kerzers 14:00 Daily 0 h 26 min · 7 stops BLS

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 13:34 from Bern · Wed 11 Nov

Next departure 13:34 today · Bern
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 10 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

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

  • Early 3% · 1
  • On time 97% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=6
  • 100% W n=6
  • 100% T n=3
  • 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, 33 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
13:34on time on time
13:39≈ 1 min early ≈ on time
13:42≈ 1 min early ≈ on time
13:45≈ 1 min early ≈ on time
13:48≈ 1 min early ≈ on time
13:53 / 13:54≈ 1 min early ≈ on time
14: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
Tue 10 NovKerzers 13:590 min—
Mon 9 NovKerzers 13:59No data—
Sun 8 NovKerzers 14:020 min—
Sat 7 NovKerzers 13:59−1 min—
Fri 6 NovKerzers 13:59−1 min—
Thu 5 NovKerzers 13:59No data—
Wed 4 NovKerzers 13:59No data—
Tue 3 NovKerzers 13:590 min—
Mon 2 NovKerzers 13:59No data—
Sun 1 NovKerzers 14:00−1 min—
Sat 31 OctKerzers 14:00−1 min—
Fri 30 OctKerzers 14:00−1 min—
Thu 29 OctKerzers 14:01No data—
Wed 28 OctKerzers 14:010 min—
Tue 27 OctKerzers 14:010 min—
Mon 26 OctKerzers 14:01No data—
Sun 25 OctKerzers 14:00−1 min—
Sat 24 OctKerzers 14:00−1 min—
Fri 23 OctKerzers 14:010 min—
Thu 22 OctKerzers 14:01No data—
Wed 21 OctKerzers 14:00−1 min—
Tue 20 OctKerzers 14:01−1 min—
Mon 19 OctKerzers 14:01No data—
Sun 18 OctKerzers 14:01−1 min—
Sat 17 OctKerzers 14:00−1 min—
Fri 16 OctKerzers 14:010 min—
Thu 15 OctKerzers 14:01No data—
Wed 14 OctKerzers 14:00−1 min—
Tue 13 OctKerzers 14:010 min—
Mon 12 OctKerzers 14:01No data—