S52 16287 Kerzers – Bern

View line S52

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

Next departure 23:00 today · Kerzers
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 24 Oct Max en route +5 min · last fix heading to Bern +5 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Bern +5 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 90% · 44
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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