S5 15868 Kerzers – Avenches

View line S5

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:35 from Kerzers · Sat 7 Nov

Next departure 18:35 today · Kerzers
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
0min
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

Worst days

  • Thu 22 Oct Max en route +32 min · last fix heading to Murten/Morat +32 min
  • Sun 27 Sept Max en route +3 min · last fix heading to Avenches +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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