S52 16222 Bern – Kerzers

View line S52

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

✓ Today’s run finished

Today it reached Kerzers at 07:00 0 min

  1. Bern06:34
  2. Bern Bümpliz Nord06:39
  3. Bern Brünnen Westside06:42
  4. Bern Riedbach06:45
  5. Rosshäusern06:48
  6. Gümmenen06:53
  7. Kerzers07:00

Next service: tomorrow 06:34 from Bern · Wed 18 Nov

Next departure 06: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%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 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

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

  • Early 2% · 1
  • On time 98% · 45
  • 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=5
  • 100% F n=6
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 46 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
06:34on time on time
06:39≈ on time ≈ on time
06:42≈ on time ≈ on time
06:45≈ on time ≈ on time
06:48≈ on time ≈ on time
06:53 / 06:54≈ on time ≈ on time
07: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
Tue 17 NovKerzers 06:590 min—
Mon 16 NovKerzers 06:590 min—
Sun 15 NovKerzers 06:59−1 min—
Sat 14 NovKerzers 06:590 min—
Fri 13 NovKerzers 06:590 min—
Thu 12 NovKerzers 07:000 min—
Wed 11 NovKerzers 06:590 min—
Tue 10 NovKerzers 06:59−1 min—
Mon 9 NovKerzers 06:590 min—
Sun 8 NovKerzers 06:59−1 min—
Sat 7 NovKerzers 06:59−1 min—
Fri 6 NovKerzers 06:590 min—
Thu 5 NovKerzers 06:590 min—
Wed 4 NovKerzers 06:590 min—
Tue 3 NovKerzers 06:590 min—
Mon 2 NovKerzers 06:590 min—
Sun 1 NovKerzers 07:000 min—
Sat 31 OctKerzers 07:010 min—
Fri 30 OctKerzers 07:00−1 min—
Thu 29 OctKerzers 07:03+2 min+2 min
Wed 28 OctKerzers 07:010 min—
Tue 27 OctKerzers 07:01−1 min—
Mon 26 OctKerzers 07:010 min—
Sun 25 OctKerzers 07:000 min—
Sat 24 OctKerzers 07:010 min—
Fri 23 OctKerzers 07:010 min—
Thu 22 OctKerzers 07:01−1 min—
Wed 21 OctKerzers 07:010 min—
Tue 20 OctKerzers 07:000 min—
Mon 19 OctKerzers 07:010 min—