S52 16267 Kerzers – Bern

View line S52

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

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

Next departure 18:00 today · Kerzers
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Tue 27 Oct Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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