S5 15876 Kerzers – Avenches

View line S5

Kerzers 20:35 → Avenches 20:53 Daily 0 h 18 min · 6 stops BLS

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 20:35 from Kerzers · Fri 20 Nov

Next departure 20:35 today · Kerzers
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
90%
56/62 runs under 3 min
RT coverage: 62 full · 0 partial · 0 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 Avenches, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 4 Oct Max en route +19 min · last fix heading to Murten/Morat +19 min
  • Fri 30 Oct Max en route +19 min · last fix heading to Murten/Morat +18 min
  • Tue 22 Sept Max en route +9 min · last fix heading to Murten/Morat +9 min
  • Mon 12 Oct Max en route +6 min · last fix heading to Avenches +6 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Avenches +5 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 87% · 54
  • 3–10 min 6% · 4
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 83% T n=12
  • 100% W n=10
  • 100% T n=10
  • 75% F n=8
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 62 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
20:35on time on time
20:39≈ on time ≈ +1 min
20:41≈ on time ≈ +1 min
20:43 / 20:45≈ on time ≈ +1 min
20:49≈ on time ≈ +1 min
20:53on 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 19 NovAvenches 20:54+1 min—
Wed 18 NovAvenches 20:530 min—
Tue 17 NovAvenches 20:540 min—
Mon 16 NovAvenches 20:54+1 min+1 min
Sun 15 NovAvenches 20:540 min—
Sat 14 NovAvenches 20:53−1 min—
Fri 13 NovAvenches 20:540 min—
Thu 12 NovAvenches 20:54−1 min—
Wed 11 NovAvenches 20:53−1 min—
Tue 10 NovAvenches 20:53−1 min—
Mon 9 NovAvenches 20:53−1 min—
Sun 8 NovAvenches 20:54−1 min—
Sat 7 NovAvenches 20:540 min—
Fri 6 NovAvenches 20:540 min—
Thu 5 NovAvenches 20:530 min—
Wed 4 NovAvenches 20:540 min—
Tue 3 NovAvenches 20:54+1 min+1 min
Mon 2 NovAvenches 20:540 min—
Sun 1 NovAvenches 20:540 min—
Sat 31 OctAvenches 20:540 min—
Fri 30 OctMurten/Morat 21:02+18 min+19 min
Thu 29 OctAvenches 20:55+1 min—
Wed 28 OctAvenches 20:54−1 min—
Tue 27 OctAvenches 20:540 min—
Mon 26 OctAvenches 20:540 min—
Sun 25 OctAvenches 20:530 min—
Sat 24 OctAvenches 20:53−1 min—
Fri 23 OctAvenches 20:58+4 min+4 min
Thu 22 OctAvenches 20:550 min—
Wed 21 OctAvenches 20:540 min—