S5 15848 Kerzers – Avenches

View line S5

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

It has not run yet today

Last recorded run: Thursday 19 November No data

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

Next departure 13:35 today · Kerzers
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 11 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 5% · 2
  • On time 95% · 41
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=9
  • 100% W n=9
  • 100% T n=4
  • 100% F n=6
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

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