S5 15821 Avenches → Kerzers

View line S5

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

S5 15821 Avenches–Kerzers: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:37 (GMT+1).

✓ Today’s run finished

Today it reached Kerzers at 06:24 0 min

  1. Avenches06:05
  2. Faoug06:08
  3. Murten/Morat06:13
  4. Muntelier-Löwenberg06:16
  5. Galmiz06:18
  6. Kerzers06:24

Next service: tomorrow 06:05 from Avenches · Mon 23 Nov

Next departure 06:05 tomorrow · Avenches
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
52/52 runs under 3 min
RT coverage: 52 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

Distribution · 90 days

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

  • Early 4% · 2
  • On time 96% · 50
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

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