S35 6537 Kerzers – Lyss
Alerts for train 6537
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S35.
It has not run yet today
Last recorded run: Saturday 7 November 0 min
Next service: today 20:06 from Kerzers · Sun 8 Nov
Last 30 days
Arrival delay at Lyss, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 23 Oct Max en route +7 min · last fix heading to Lyss +7 min
- Tue 20 Oct Max en route +4 min · last fix heading to Lyss +4 min
- Thu 22 Oct Max en route +4 min · last fix heading to Lyss +4 min
- Wed 14 Oct Max en route +3 min · last fix heading to Lyss +3 min
Distribution · 90 days
35 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 31
- 3–10 min 11% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 80% T n=5
- 80% W n=5
- 80% T n=5
- 80% F n=5
- 100% S n=5
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 35 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 |
|---|---|---|---|
| 20:06 | on time | on time | |
| 20:08 | ≈ on time | ≈ on time | |
| 20:10 | ≈ on time | ≈ +1 min | |
| 20:13 / 20:14 | ≈ on time | ≈ +1 min | |
| 20:16 / 20:17 | ≈ on time | ≈ +1 min | |
| 20:19 | ≈ on time | ≈ +2 min | |
| 20:22 | ≈ on time | ≈ +2 min | |
| 20:26 | +1 min | +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 | Lyss 20:24 | 0 min | — |
| Fri 6 Nov | Lyss 20:28 | +1 min | +1 min |
| Thu 5 Nov | Lyss 20:27 | 0 min | — |
| Wed 4 Nov | Lyss 20:27 | 0 min | — |
| Tue 3 Nov | Lyss 20:28 | 0 min | — |
| Mon 2 Nov | Lyss 20:27 | 0 min | — |
| Sun 1 Nov | Lyss 20:28 | +1 min | — |
| Sat 31 Oct | Lyss 20:27 | +1 min | — |
| Fri 30 Oct | Lyss 20:28 | +1 min | — |
| Thu 29 Oct | Lyss 20:27 | 0 min | — |
| Wed 28 Oct | Lyss 20:28 | +1 min | — |
| Tue 27 Oct | Lyss 20:28 | +1 min | +1 min |
| Mon 26 Oct | Lyss 20:28 | +1 min | +1 min |
| Sun 25 Oct | Lyss 20:27 | +1 min | — |
| Sat 24 Oct | Lyss 20:28 | +1 min | — |
| Fri 23 Oct | Lyss 20:34 | +7 min | +7 min |
| Thu 22 Oct | Lyss 20:31 | +4 min | +4 min |
| Wed 21 Oct | Lyss 20:27 | 0 min | — |
| Tue 20 Oct | Lyss 20:31 | +4 min | +4 min |
| Mon 19 Oct | Lyss 20:27 | +1 min | — |
| Sun 18 Oct | Lyss 20:28 | +1 min | — |
| Sat 17 Oct | Lyss 20:27 | 0 min | — |
| Fri 16 Oct | Lyss 20:28 | 0 min | — |
| Thu 15 Oct | Lyss 20:29 | +2 min | +2 min |
| Wed 14 Oct | Lyss 20:31 | +3 min | +3 min |
| Tue 13 Oct | Lyss 20:27 | 0 min | — |
| Mon 12 Oct | Lyss 20:27 | 0 min | — |
| Sun 11 Oct | Lyss 20:27 | 0 min | — |
| Sat 10 Oct | Lyss 20:28 | +1 min | — |
| Fri 9 Oct | Lyss 20:29 | +1 min | +1 min |