S5 15873 Avenches → Kerzers

View line S5

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

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 19:05 from Avenches · Sat 21 Nov

Next departure 19:05 today · Avenches
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
94%
45/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 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

Worst days

  • Thu 22 Oct Max en route +15 min · last fix heading to Kerzers +15 min
  • Mon 16 Nov Max en route +9 min · last fix heading to Kerzers +9 min
  • Fri 23 Oct Max en route +7 min · last fix heading to Kerzers +7 min

Distribution · 90 days

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

  • Early 8% · 4
  • On time 85% · 41
  • 3–10 min 4% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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