S5 15888 Kerzers → Avenches

View line S5

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

S5 15888 Kerzers–Avenches: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Avenches: 23:53. TrainsRadar data as of 21 Nov 2026, 23:53 (GMT+1).

Running now · updated 23:52

Position estimated from the timetable

Between Faoug and Avenches −1 min

Estimated arrival at Avenches 23:53 · 20 km/h

  1. Kerzers23:35
  2. Galmiz23:39
  3. Muntelier-Löwenberg23:41
  4. Murten/Morat23:43
  5. Faoug23:49
  6. Avenches23:53

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

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%
60/60 runs under 3 min
RT coverage: 60 full · 0 partial · 1 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: 0 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

Distribution · 90 days

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

  • Early 10% · 6
  • On time 90% · 54
  • 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=9
  • 100% W n=9
  • 100% T n=8
  • 100% F n=10
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 60 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 10Today
23:35on time on timePassed
23:39≈ on time ≈ on timePassed
23:41≈ on time ≈ on timePassed
23:43 / 23:45≈ on time ≈ on timePassed
23:49≈ on time ≈ on timePassed
23:53on time +1 minNext

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
Sat 21 NovAvenches 23:490 min—
Fri 20 NovAvenches 23:53−1 min—
Thu 19 NovAvenches 23:540 min—
Wed 18 NovAvenches 23:53−1 min—
Tue 17 NovAvenches 23:54+2 min+2 min
Mon 16 NovAvenches 23:54+1 min—
Sun 15 NovAvenches 23:540 min—
Sat 14 NovAvenches 23:540 min—
Fri 13 NovAvenches 23:540 min—
Thu 12 NovAvenches 23:54−1 min—
Wed 11 NovAvenches 23:53−1 min—
Tue 10 NovAvenches 23:540 min—
Mon 9 NovAvenches 23:540 min—
Sun 8 NovAvenches 23:540 min—
Sat 7 NovAvenches 23:53−1 min—
Fri 6 NovAvenches 23:54−1 min—
Thu 5 NovAvenches 23:530 min—
Wed 4 NovAvenches 23:540 min—
Tue 3 NovAvenches 23:540 min—
Mon 2 NovAvenches 23:54−1 min—
Sun 1 NovAvenches 23:53−1 min—
Sat 31 OctAvenches 23:540 min—
Fri 30 OctAvenches 23:53−1 min—
Thu 29 OctAvenches 23:53−1 min—
Wed 28 OctAvenches 23:540 min—
Tue 27 OctAvenches 23:540 min—
Mon 26 OctAvenches 23:55+1 min—
Sun 25 OctAvenches 23:540 min—
Sat 24 OctAvenches 23:53−1 min—
Fri 23 OctAvenches 23:53−1 min—