S52 16247 Kerzers – Bern

View line S52

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

✓ Today’s run finished

Today it reached Bern at 13:26 0 min

  1. Kerzers13:00
  2. Gümmenen13:05
  3. Rosshäusern13:10
  4. Bern Riedbach13:13
  5. Bern Brünnen Westside13:16
  6. Bern Bümpliz Nord13:19
  7. Bern13:26

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

Next departure 13:00 tomorrow · Kerzers
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 8 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, 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=2
  • 100% T n=9
  • 100% W n=5
  • 100% T n=2
  • 100% F n=5
  • 100% S n=5
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
13:00on time on time
13:05≈ on time ≈ on time
13:10≈ on time ≈ +1 min
13:13≈ on time ≈ +1 min
13:16 / 13:17≈ on time ≈ +1 min
13:19 / 13:20≈ on time ≈ +1 min
13:26on 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
Fri 6 NovBern 13:270 min—
Thu 5 NovBern 13:27No data—
Wed 4 NovBern 13:270 min—
Tue 3 NovBern 13:270 min—
Mon 2 NovBern 13:27No data—
Sun 1 NovBern 13:28+1 min—
Sat 31 OctBern 13:28+2 min+2 min
Fri 30 OctBern 13:28+1 min+1 min
Thu 29 OctBern 13:27No data—
Wed 28 OctBern 13:270 min—
Tue 27 OctBern 13:280 min—
Mon 26 OctBern 13:27No data—
Sun 25 OctBern 13:26−1 min—
Sat 24 OctBern 13:270 min—
Fri 23 OctBern 13:29+2 min+2 min
Thu 22 OctBern 13:27No data—
Wed 21 OctBern 13:28+1 min—
Tue 20 OctBern 13:29+2 min+2 min
Mon 19 OctBern 13:27No data—
Sun 18 OctBern 13:270 min—
Sat 17 OctBern 13:28+1 min+1 min
Fri 16 OctBern 13:270 min—
Thu 15 OctBern 13:27No data—
Wed 14 OctBern 13:270 min—
Tue 13 OctBern 13:280 min—
Mon 12 OctBern 13:27No data—
Sun 11 OctBern 13:270 min—
Sat 10 OctBern 13:270 min—
Fri 9 OctBern 13:28+1 min—
Thu 8 OctBern 13:28+1 min—