S52 16251 Kerzers – Bern

View line S52

Kerzers 14:00 → Bern 14:26 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 14:00 from Kerzers · Wed 11 Nov

Next departure 14:00 today · Kerzers
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 9 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

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 94% · 33
  • 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=8
  • 100% W n=6
  • 100% T n=1
  • 100% F n=6
  • 100% S n=6
  • 100% S n=6

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
14:00on time on time
14:05≈ on time ≈ on time
14:10≈ on time ≈ on time
14:13≈ on time ≈ on time
14:16 / 14:17≈ on time ≈ on time
14:19 / 14:20≈ on time ≈ +1 min
14:26on 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
Tue 10 NovBern 14:270 min—
Mon 9 NovBern 14:27No data—
Sun 8 NovBern 14:28+1 min—
Sat 7 NovBern 14:28+1 min+1 min
Fri 6 NovBern 14:270 min—
Thu 5 NovBern 14:27No data—
Wed 4 NovBern 14:270 min—
Tue 3 NovBern 14:280 min—
Mon 2 NovBern 14:27No data—
Sun 1 NovBern 14:270 min—
Sat 31 OctBern 14:270 min—
Fri 30 OctBern 14:270 min—
Thu 29 OctBern 14:27No data—
Wed 28 OctBern 14:270 min—
Tue 27 OctBern 14:270 min—
Mon 26 OctBern 14:27No data—
Sun 25 OctBern 14:260 min—
Sat 24 OctBern 14:26−1 min—
Fri 23 OctBern 14:26−1 min—
Thu 22 OctBern 14:27No data—
Wed 21 OctBern 14:270 min—
Tue 20 OctBern 14:270 min—
Mon 19 OctBern 14:27No data—
Sun 18 OctBern 14:270 min—
Sat 17 OctBern 14:28+1 min—
Fri 16 OctBern 14:27−1 min—
Thu 15 OctBern 14:27No data—
Wed 14 OctBern 14:270 min—
Mon 12 OctBern 14:27No data—
Sun 11 OctBern 14:26−1 min—