S5 15844 Kerzers – Avenches

View line S5

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

✓ Today’s run finished

Today, last fix heading to Avenches at 12:54 No data

  1. Kerzers12:35
  2. Galmiz12:39
  3. Muntelier-Löwenberg12:41
  4. Murten/Morat12:43
  5. Faoug12:49
  6. Avenches12:53

Next service: tomorrow 12:35 from Kerzers · Tue 17 Nov

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

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

  • Early 5% · 2
  • On time 95% · 38
  • 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=8
  • 100% W n=7
  • 100% T n=3
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

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