S5 15877 Avenches – Kerzers

View line S5

Avenches 20:05 → Kerzers 20:24 Daily 0 h 19 min · 6 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 20:24 0 min

  1. Avenches20:05
  2. Faoug20:08
  3. Murten/Morat20:13
  4. Muntelier-Löwenberg20:16
  5. Galmiz20:18
  6. Kerzers20:24

Next service: tomorrow 20:05 from Avenches · Sun 8 Nov

Next departure 20:05 tomorrow · Avenches
On-time · 30 days
83%
25/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
88%
35/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Kerzers, 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 30 Oct Max en route +8 min · last fix heading to Kerzers +8 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Kerzers +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Kerzers +5 min
  • Wed 21 Oct Max en route +4 min · last fix heading to Kerzers +4 min
  • Thu 22 Oct Max en route +4 min · last fix heading to Kerzers +4 min

Distribution · 90 days

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

  • Early 10% · 4
  • On time 78% · 31
  • 3–10 min 13% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 80% W n=5
  • 80% T n=5
  • 60% F n=5
  • 100% S n=6
  • 100% S n=6

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
20:05on time on time
20:08≈ on time ≈ +1 min
20:13 / 20:14≈ on time ≈ +2 min
20:16≈ on time ≈ +3 min
20:18≈ on time ≈ +3 min
20:24on time +4 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
Sat 7 NovKerzers 20:240 min—
Fri 6 NovKerzers 20:24+1 min—
Thu 5 NovKerzers 20:24+1 min—
Wed 4 NovKerzers 20:24−1 min—
Tue 3 NovKerzers 20:240 min—
Mon 2 NovKerzers 20:240 min—
Sun 1 NovKerzers 20:240 min—
Sat 31 OctKerzers 20:24−1 min—
Fri 30 OctKerzers 20:33+8 min+8 min
Thu 29 OctKerzers 20:26+1 min—
Wed 28 OctKerzers 20:24−1 min—
Tue 27 OctKerzers 20:24−1 min—
Mon 26 OctKerzers 20:250 min—
Sun 25 OctKerzers 20:240 min—
Sat 24 OctKerzers 20:26+1 min—
Fri 23 OctKerzers 20:30+5 min+5 min
Thu 22 OctKerzers 20:29+4 min+4 min
Wed 21 OctKerzers 20:29+4 min+4 min
Tue 20 OctKerzers 20:30+5 min+5 min
Mon 19 OctKerzers 20:240 min—
Sun 18 OctKerzers 20:24−1 min—
Sat 17 OctKerzers 20:250 min—
Fri 16 OctKerzers 20:26+1 min—
Thu 15 OctKerzers 20:26+1 min—
Wed 14 OctKerzers 20:24−1 min—
Tue 13 OctKerzers 20:26+1 min—
Mon 12 OctKerzers 20:250 min—
Sun 11 OctKerzers 20:250 min—
Sat 10 OctKerzers 20:250 min—
Fri 9 OctKerzers 20:25−1 min—