S5 15832 Kerzers – Avenches

View line S5

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

Running now · updated 09:37

Position estimated from the timetable

Between Kerzers and Galmiz 0 min

Estimated arrival at Avenches 09:53 · 74 km/h

  1. Kerzers09:35
  2. Galmiz09:39
  3. Muntelier-Löwenberg09:41
  4. Murten/Morat09:43
  5. Faoug09:49
  6. Avenches09:53

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 27 runs arrived on time.

On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Fri 28 Aug Max en route +6 min · last fix heading to Murten/Morat +6 min

Distribution · 90 days

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

  • Early 12% · 6
  • On time 86% · 42
  • 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=7
  • 100% W n=6
  • 100% T n=5
  • 88% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

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