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