S5 15852 Kerzers → Avenches

View line S5

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

It has not run yet today

Last recorded run: Friday 20 November +3 min

Next service: today 14:35 from Kerzers · Sat 21 Nov

Next departure 14:35 today · Kerzers
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 4 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 51 full · 0 partial · 6 no data
Typical delay
−1min
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

  • Fri 20 Nov Max en route +3 min · last fix heading to Avenches +3 min

Distribution · 90 days

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

  • Early 14% · 7
  • On time 84% · 43
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=10
  • 100% W n=8
  • 100% T n=4
  • 86% F n=7
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

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