S52 16275 Kerzers – Bern

View line S52

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:00 from Kerzers · Sun 8 Nov

Next departure 20:00 today · Kerzers
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
95%
40/42 runs under 3 min
RT coverage: 42 full · 0 partial · 1 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

  • Fri 30 Oct Max en route +23 min · last fix heading to Bern +23 min
  • Fri 23 Oct Max en route +13 min · last fix heading to Bern +13 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 90% · 38
  • 3–10 min 0% · 0
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=4
  • 67% F n=6
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

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