S5 15841 Avenches – Kerzers

View line S5

Avenches 11:05 → Kerzers 11:24 Daily 0 h 19 min · 6 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:05 from Avenches · Thu 5 Nov

Next departure 11:05 today · Avenches
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 7 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 7 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: +1 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

Distribution · 90 days

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

  • Early 7% · 2
  • On time 93% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=6
  • 100% T n=2
  • 100% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

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