S5 15836 Kerzers – Avenches

View line S5

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 10:35 from Kerzers · Wed 18 Nov

Next departure 10:35 today · Kerzers
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
98%
49/50 runs under 3 min
RT coverage: 50 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 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

Worst days

  • Wed 26 Aug Max en route +5 min · last fix heading to Faoug +5 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 92% · 46
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 86% W n=7
  • 100% T n=6
  • 100% F n=7
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

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