S5 15593 Kerzers – Bern

View line S5

Kerzers 00:38 → Bern 01:02 Daily 0 h 24 min · 7 stops BLS

✓ Today’s run finished

Today it reached Bern at 01:02 0 min

  1. Kerzers00:38
  2. Gümmenen00:43
  3. Rosshäusern00:48
  4. Bern Riedbach00:51
  5. Bern Brünnen Westside00:54
  6. Bern Bümpliz Nord00:56
  7. Bern01:02

Next service: tomorrow 00:38 from Kerzers · Tue 17 Nov

Next departure 00:38 tomorrow · Kerzers
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
71/74 runs under 3 min
RT coverage: 74 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 15 Oct Max en route +13 min · last fix heading to Bern +13 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Bern +5 min
  • Wed 21 Oct Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 95% · 70
  • 3–10 min 3% · 2
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 91% W n=11
  • 91% T n=11
  • 100% F n=12
  • 100% S n=9
  • 100% S n=11

Stops and timetable

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

Last 90 days, 74 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:38on time +1 min
00:43≈ on time ≈ +1 min
00:48≈ on time ≈ +1 min
00:51≈ on time ≈ +1 min
00:54 / 00:55≈ on time ≈ +1 min
00:56 / 00:57≈ on time ≈ +1 min
01:02on time +2 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
Mon 16 NovBern 01:030 min—
Sun 15 NovBern 01:040 min—
Sat 14 NovBern 01:030 min—
Fri 13 NovBern 01:04+1 min+1 min
Thu 12 NovBern 01:030 min—
Wed 11 NovBern 01:04+2 min+2 min
Tue 10 NovBern 01:04+1 min+1 min
Mon 9 NovBern 01:040 min—
Sun 8 NovBern 01:020 min—
Sat 7 NovBern 01:04+1 min+1 min
Fri 6 NovBern 01:030 min—
Thu 5 NovBern 01:030 min—
Wed 4 NovBern 01:030 min—
Tue 3 NovBern 01:04+2 min+2 min
Mon 2 NovBern 01:030 min—
Sun 1 NovBern 01:04+1 min+1 min
Sat 31 OctBern 01:030 min—
Fri 30 OctBern 01:04+1 min+1 min
Thu 29 OctBern 01:040 min—
Wed 28 OctBern 01:05+2 min+2 min
Tue 27 OctBern 01:04+1 min—
Mon 26 OctBern 01:030 min—
Sun 25 OctBern 01:04+1 min+1 min
Sat 24 OctBern 01:05+2 min+2 min
Fri 23 OctBern 01:030 min—
Thu 22 OctBern 01:03+1 min—
Wed 21 OctBern 01:07+4 min+4 min
Tue 20 OctBern 01:030 min—
Mon 19 OctBern 01:040 min—
Sun 18 OctBern 01:030 min—