S5 15892 Kerzers → Avenches

View line S5

Kerzers 00:35 → Avenches 00:53 Daily 0 h 18 min · 6 stops BLS

S5 15892 Kerzers–Avenches: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 16:05 (GMT+1).

✓ Today’s run finished

Today it reached Avenches at 00:53 0 min

  1. Kerzers00:35
  2. Galmiz00:39
  3. Muntelier-Löwenberg00:41
  4. Murten/Morat00:43
  5. Faoug00:49
  6. Avenches00:53

Next service: tomorrow 00:35 from Kerzers · Mon 23 Nov

Next departure 00:35 tomorrow · Kerzers
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
99%
66/67 runs under 3 min
RT coverage: 67 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Avenches, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 16 Nov Max en route +8 min · last fix heading to Avenches +8 min

Distribution · 90 days

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

  • Early 10% · 7
  • On time 88% · 59
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=8
  • 100% W n=9
  • 100% T n=10
  • 100% F n=12
  • 100% S n=9
  • 100% S n=10

Stops and timetable

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

Last 90 days, 67 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
00:35on time on time
00:39≈ on time ≈ on time
00:41≈ on time ≈ on time
00:43 / 00:45≈ on time ≈ on time
00:49≈ on time ≈ +1 min
00:531 min early +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 NovAvenches 00:540 min—
Sat 21 NovAvenches 00:53−1 min—
Fri 20 NovAvenches 00:53−1 min—
Thu 19 NovAvenches 00:54−1 min—
Wed 18 NovAvenches 00:53−1 min—
Tue 17 NovAvenches 00:53−1 min—
Mon 16 NovAvenches 01:02+8 min+8 min
Sun 15 NovAvenches 00:54−1 min—
Sat 14 NovAvenches 00:54−1 min—
Fri 13 NovAvenches 00:54−1 min—
Thu 12 NovAvenches 00:540 min—
Wed 11 NovAvenches 00:54−1 min—
Tue 10 NovAvenches 00:54−1 min—
Mon 9 NovAvenches 00:540 min—
Sun 8 NovAvenches 00:53−1 min—
Sat 7 NovAvenches 00:54+2 min+2 min
Fri 6 NovAvenches 00:53−1 min—
Thu 5 NovAvenches 00:53−1 min—
Wed 4 NovAvenches 00:540 min—
Tue 3 NovAvenches 00:54+1 min+1 min
Mon 2 NovAvenches 00:54−1 min—
Sun 1 NovAvenches 00:530 min—
Sat 31 OctAvenches 00:53−1 min—
Fri 30 OctAvenches 00:540 min—
Thu 29 OctAvenches 00:53−1 min—
Wed 28 OctAvenches 00:540 min—
Tue 27 OctAvenches 00:53−1 min—
Mon 26 OctAvenches 00:53−1 min—
Sun 25 OctAvenches 00:540 min—
Sat 24 OctAvenches 00:56+2 min+2 min