S52 16218 Bern – Kerzers

View line S52

Bern 05:34 → Kerzers 06:00 Daily 0 h 26 min · 7 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 06:00 0 min

  1. Bern05:34
  2. Bern Bümpliz Nord05:39
  3. Bern Brünnen Westside05:42
  4. Bern Riedbach05:45
  5. Rosshäusern05:48
  6. Gümmenen05:53
  7. Kerzers06:00

Next service: tomorrow 05:34 from Bern · Sun 8 Nov

Next departure 05:34 tomorrow · Bern
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Kerzers, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
05:34on time on time
05:39≈ on time ≈ on time
05:42≈ on time ≈ on time
05:45≈ on time ≈ on time
05:48≈ on time ≈ on time
05:53 / 05:54≈ on time ≈ on time
06:00on time on time

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 NovKerzers 05:590 min—
Fri 6 NovKerzers 05:590 min—
Thu 5 NovKerzers 05:590 min—
Wed 4 NovKerzers 05:59−1 min—
Tue 3 NovKerzers 06:020 min—
Mon 2 NovKerzers 05:590 min—
Sun 1 NovKerzers 06:00−1 min—
Sat 31 OctKerzers 06:00−1 min—
Fri 30 OctKerzers 06:010 min—
Thu 29 OctKerzers 06:00−1 min—
Wed 28 OctKerzers 06:010 min—
Tue 27 OctKerzers 06:010 min—
Mon 26 OctKerzers 06:03+2 min+2 min
Sun 25 OctKerzers 06:010 min—
Sat 24 OctKerzers 06:010 min—
Fri 23 OctKerzers 06:00−1 min—
Thu 22 OctKerzers 06:010 min—
Wed 21 OctKerzers 06:010 min—
Tue 20 OctKerzers 06:00−1 min—
Mon 19 OctKerzers 06:00−1 min—
Sun 18 OctKerzers 06:01−1 min—
Sat 17 OctKerzers 06:01−1 min—
Fri 16 OctKerzers 06:000 min—
Thu 15 OctKerzers 06:04+2 min+2 min
Wed 14 OctKerzers 06:00−1 min—
Tue 13 OctKerzers 06:00−1 min—
Mon 12 OctKerzers 06:00−1 min—
Sun 11 OctKerzers 06:010 min—
Sat 10 OctKerzers 06:02+1 min—
Fri 9 OctKerzers 06:00−1 min—