S5 15840 Kerzers – Avenches

View line S5

Kerzers 11:35 → Avenches 11:53 Daily 0 h 18 min · 6 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November −1 min

Next service: today 11:35 from Kerzers · Thu 5 Nov

Next departure 11:35 today · Kerzers
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 8 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 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

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

  • Early 10% · 3
  • On time 90% · 28
  • 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=6
  • 100% W n=7
  • 100% T n=1
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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