S5 15872 Kerzers – Avenches
Alerts for train 15872
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S5.
✓ Today’s run finished
Today it reached Avenches at 19:54 +1 min
- Kerzers19:35
- Galmiz19:39
- Muntelier-Löwenberg19:41
- Murten/Morat19:43
- Faoug19:49
- Avenches19:53
Next service: tomorrow 19:35 from Kerzers · Sun 8 Nov
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
- Thu 22 Oct Max en route +10 min · last fix heading to Avenches +10 min
- Tue 6 Oct Max en route +3 min · last fix heading to Avenches +3 min
- Wed 14 Oct Max en route +3 min · last fix heading to Avenches +3 min
- Fri 28 Aug Max en route +6 min · last fix heading to Avenches +3 min
Distribution · 90 days
45 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 4% · 2
- On time 87% · 39
- 3–10 min 9% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 83% T n=6
- 83% W n=6
- 83% T n=6
- 86% F n=7
- 100% S n=5
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 45 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 19:35 | on time | on time | |
| 19:39 | ≈ on time | ≈ +1 min | |
| 19:41 | ≈ on time | ≈ +1 min | |
| 19:43 / 19:45 | ≈ on time | ≈ +1 min | |
| 19:49 | ≈ on time | ≈ +2 min | |
| 19:53 | on time | +3 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Avenches 19:54 | +1 min | — |
| Fri 6 Nov | Avenches 19:54 | +1 min | +1 min |
| Thu 5 Nov | Avenches 19:54 | 0 min | — |
| Wed 4 Nov | Avenches 19:57 | +3 min | +3 min |
| Tue 3 Nov | Avenches 19:54 | 0 min | — |
| Mon 2 Nov | Avenches 19:54 | +1 min | — |
| Sun 1 Nov | Avenches 19:54 | −1 min | — |
| Sat 31 Oct | Avenches 19:53 | −1 min | — |
| Fri 30 Oct | Avenches 19:55 | +1 min | — |
| Thu 29 Oct | Avenches 19:54 | 0 min | — |
| Wed 28 Oct | Avenches 19:54 | 0 min | — |
| Tue 27 Oct | Avenches 19:53 | −1 min | — |
| Mon 26 Oct | Avenches 19:55 | +1 min | — |
| Sun 25 Oct | Avenches 19:53 | −1 min | — |
| Sat 24 Oct | Avenches 19:54 | 0 min | — |
| Fri 23 Oct | Avenches 19:57 | +3 min | +3 min |
| Thu 22 Oct | Avenches 20:04 | +10 min | +10 min |
| Wed 21 Oct | Avenches 19:55 | +2 min | +2 min |
| Tue 20 Oct | Avenches 19:56 | +1 min | +1 min |
| Mon 19 Oct | Avenches 19:54 | 0 min | — |
| Sun 18 Oct | Avenches 19:54 | 0 min | — |
| Sat 17 Oct | Avenches 19:53 | −1 min | — |
| Fri 16 Oct | Avenches 19:54 | −1 min | — |
| Thu 15 Oct | Avenches 19:54 | 0 min | — |
| Wed 14 Oct | Avenches 19:57 | +3 min | +3 min |
| Tue 13 Oct | Avenches 19:54 | −1 min | — |
| Mon 12 Oct | Avenches 19:54 | 0 min | — |
| Sun 11 Oct | Avenches 19:53 | −1 min | — |
| Sat 10 Oct | Avenches 19:54 | 0 min | — |
| Fri 9 Oct | Avenches 19:55 | 0 min | — |