S5 15849 Avenches – Kerzers

View line S5

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 13:05 from Avenches · Wed 18 Nov

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

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

  • Early 6% · 2
  • On time 94% · 34
  • 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=7
  • 100% W n=7
  • 100% T n=2
  • 100% F n=6
  • 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, 36 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
13:05on time on time
13:08≈ on time ≈ on time
13:13 / 13:14≈ on time ≈ on time
13:16≈ on time ≈ on time
13:18≈ on time ≈ on time
13:24on 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
Tue 17 NovKerzers 13:240 min—
Mon 16 NovKerzers 13:24No data—
Sun 15 NovKerzers 13:24−1 min—
Sat 14 NovKerzers 13:240 min—
Fri 13 NovKerzers 13:240 min—
Thu 12 NovKerzers 13:24No data—
Wed 11 NovKerzers 13:240 min—
Tue 10 NovKerzers 13:240 min—
Mon 9 NovKerzers 13:24No data—
Sun 8 NovKerzers 13:24−1 min—
Sat 7 NovKerzers 13:240 min—
Fri 6 NovKerzers 13:240 min—
Thu 5 NovKerzers 13:24No data—
Wed 4 NovKerzers 13:240 min—
Tue 3 NovKerzers 13:240 min—
Mon 2 NovKerzers 13:24No data—
Sun 1 NovKerzers 13:240 min—
Sat 31 OctKerzers 13:250 min—
Fri 30 OctKerzers 13:24−1 min—
Thu 29 OctKerzers 13:25No data—
Wed 28 OctKerzers 13:250 min—
Tue 27 OctKerzers 13:250 min—
Mon 26 OctKerzers 13:25No data—
Sun 25 OctKerzers 13:250 min—
Sat 24 OctKerzers 13:250 min—
Fri 23 OctKerzers 13:25+1 min—
Thu 22 OctKerzers 13:25No data—
Wed 21 OctKerzers 13:26+1 min—
Tue 20 OctKerzers 13:250 min—
Mon 19 OctKerzers 13:25No data—