S52 16739 Kerzers – Bern Brünnen Westside

View line S52

Kerzers 00:04 → Bern Brünnen Westside 00:20 Daily 0 h 16 min · 5 stops BLS

It has not run yet today

Last recorded run: Thursday 5 November +1 min

Next service: tomorrow 00:04 from Kerzers · Sat 7 Nov

Next departure 00:04 tomorrow · Kerzers
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 25 full · 3 partial · 1 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 31 full · 3 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 Brünnen Westside, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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
00:04+1 min +1 min
00:08 / 00:09≈ on time ≈ +1 min
00:14≈ on time ≈ +1 min
00:16≈ on time ≈ +1 min
00:20on 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
Thu 5 NovKerzers 10:54Partial coverage+1 min—
Wed 4 NovKerzers 10:54Partial coverage+1 min—
Tue 3 NovKerzers 10:57Partial coverage+2 min+2 min
Mon 2 NovKerzers 10:540 min—
Sun 1 NovKerzers 10:540 min—
Sat 31 OctKerzers 10:550 min—
Fri 30 OctKerzers 10:550 min—
Thu 29 OctKerzers 10:55No data—
Wed 28 OctKerzers 10:550 min—
Tue 27 OctKerzers 10:550 min—
Mon 26 OctMurten/Morat 11:010 min—
Sun 25 OctKerzers 10:550 min—
Sat 24 OctKerzers 10:54−1 min—
Fri 23 OctKerzers 10:550 min—
Thu 22 OctKerzers 10:550 min—
Wed 21 OctKerzers 10:57+2 min+2 min
Tue 20 OctKerzers 10:550 min—
Mon 19 OctKerzers 10:54−1 min—
Sun 18 OctKerzers 10:55−1 min—
Sat 17 OctKerzers 10:550 min—
Fri 16 OctKerzers 10:55+1 min—
Thu 15 OctKerzers 10:56+1 min—
Wed 14 OctKerzers 10:550 min—
Tue 13 OctKerzers 10:550 min—
Mon 12 OctKerzers 10:56+1 min—
Sun 11 OctKerzers 10:550 min—
Sat 10 OctKerzers 10:550 min—
Fri 9 OctKerzers 10:550 min—
Thu 8 OctKerzers 10:56+1 min+1 min
Wed 7 OctKerzers 10:56+1 min—