S52 16283 Kerzers – Bern

View line S52

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 22:00 from Kerzers · Sat 7 Nov

Next departure 22:00 today · Kerzers
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 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

Distribution · 90 days

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

  • Early 5% · 2
  • On time 95% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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