Train NS 9060 Leeuwarden – Lelystad Centrum
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 16:03 from Leeuwarden · Fri 6 Nov
Last 30 days
Arrival delay at Lelystad Centrum, 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 5 Oct Max en route +6 min · last fix heading to Dronten +4 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 19
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=4
- 100% W n=2
- 100% T n=2
- 100% F n=2
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 20 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 |
|---|---|---|---|
| 16:03 | on time | on time | |
| 16:12 | ≈ on time | ≈ on time | |
| 16:16 | ≈ on time | ≈ on time | |
| 16:23 | ≈ on time | ≈ on time | |
| 16:30 | ≈ on time | ≈ on time | |
| 16:38 | ≈ on time | ≈ on time | |
| 16:47 | ≈ on time | ≈ on time | |
| 17:02 / 17:07 | ≈ on time | ≈ on time | |
| 17:17 | ≈ on time | ≈ on time | |
| 17:25 | ≈ on time | ≈ on time | |
| 17:38 | on time | on time |
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 |
|---|---|---|---|
| Thu 5 Nov | Dronten 17:39 | No data | — |
| Wed 4 Nov | Dronten 17:39Partial coverage | 0 min | — |
| Tue 3 Nov | Dronten 17:39Partial coverage | 0 min | — |
| Mon 2 Nov | Dronten 17:39Partial coverage | 0 min | — |
| Sun 1 Nov | Dronten 17:40 | 0 min | — |
| Sat 31 Oct | Dronten 17:39 | 0 min | — |
| Fri 30 Oct | Dronten 17:39 | No data | — |
| Thu 29 Oct | Dronten 17:39 | No data | — |
| Wed 28 Oct | Dronten 17:39 | No data | — |
| Tue 27 Oct | Dronten 17:50 | No data | — |
| Mon 26 Oct | Dronten 17:48 | No data | — |
| Sun 25 Oct | Dronten 17:39 | No data | — |
| Sat 24 Oct | Dronten 17:39 | 0 min | — |
| Fri 23 Oct | Dronten 17:49 | No data | — |
| Thu 22 Oct | Dronten 17:40Partial coverage | 0 min | — |
| Wed 21 Oct | Dronten 17:40 | No data | — |
| Tue 20 Oct | Dronten 17:39Partial coverage | 0 min | — |
| Mon 19 Oct | Dronten 17:40Partial coverage | 0 min | — |
| Sun 18 Oct | Dronten 17:40 | 0 min | — |
| Sat 17 Oct | Dronten 17:40 | No data | — |
| Fri 16 Oct | Dronten 17:39Partial coverage | 0 min | — |
| Thu 15 Oct | Dronten 17:54 | No data | — |
| Wed 14 Oct | Dronten 17:40 | No data | — |
| Tue 13 Oct | Dronten 17:42Partial coverage | 0 min | — |
| Mon 12 Oct | Dronten 17:40 | 0 min | — |
| Sun 11 Oct | Dronten 17:39 | 0 min | — |
| Sat 10 Oct | Dronten 17:39 | 0 min | — |
| Fri 9 Oct | Dronten 17:39Partial coverage | 0 min | — |
| Thu 8 Oct | Dronten 17:40Partial coverage | 0 min | — |
| Wed 7 Oct | Dronten 17:40Partial coverage | 0 min | — |