Train NS 9070 Leeuwarden – Lelystad Centrum
Running now · updated 19:54
Heading to Lelystad Centrum 0 min
Estimated arrival at Lelystad Centrum 20:08 · 46 km/h
- Leeuwarden18:33
- Akkrum18:46
- Heerenveen18:53
- Steenwijk19:08
- Zwolle19:32
- Kampen Zuid19:47
- Lelystad Centrum20:08
Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 15 runs arrived on time.
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
- Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 17
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 100% W n=3
- 50% T n=2
- 100% F n=3
- 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, 18 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 | Today |
|---|---|---|---|---|
| 18:33 | on time | on time | ||
| 18:42 | ≈ on time | ≈ on time | ||
| 18:46 | ≈ on time | ≈ on time | ||
| 18:53 | ≈ on time | ≈ +1 min | ||
| 19:00 | ≈ on time | ≈ +1 min | ||
| 19:08 | ≈ on time | ≈ +1 min | ||
| 19:17 | ≈ on time | ≈ +1 min | ||
| 19:32 / 19:37 | ≈ on time | ≈ +1 min | ||
| 19:47 | ≈ on time | ≈ +2 min | ||
| 19:55 | ≈ on time | ≈ +2 min | ||
| 20:08 | on time | +2 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 |
|---|---|---|---|
| Fri 6 Nov | Akkrum 19:49Partial coverage | 0 min | — |
| Thu 5 Nov | — 20:09 | No data | — |
| Wed 4 Nov | — 20:09 | 0 min | — |
| Tue 3 Nov | — 20:09 | No data | — |
| Sun 1 Nov | Dronten 20:09Partial coverage | 0 min | — |
| Sat 31 Oct | Dronten 20:09 | 0 min | — |
| Fri 30 Oct | Heerenveen 20:09 | No data | — |
| Thu 29 Oct | — 20:09 | +4 min | +4 min |
| Wed 28 Oct | — 20:09 | No data | — |
| Tue 27 Oct | — 20:09 | No data | — |
| Mon 26 Oct | Kampen Zuid 20:09 | 0 min | — |
| Sun 25 Oct | Dronten 20:09 | No data | — |
| Sat 24 Oct | Dronten 20:09 | 0 min | — |
| Fri 23 Oct | Meppel 20:09Partial coverage | 0 min | — |
| Thu 22 Oct | Grou-Jirnsum 20:10 | No data | — |
| Wed 21 Oct | Leeuwarden 20:18 | No data | — |
| Tue 20 Oct | Akkrum 20:16Partial coverage | 0 min | — |
| Mon 19 Oct | Grou-Jirnsum 20:10 | No data | — |
| Sun 18 Oct | Dronten 20:10Partial coverage | 0 min | — |
| Sat 17 Oct | Dronten 20:10 | No data | — |
| Fri 16 Oct | Dronten 20:09 | No data | — |
| Thu 15 Oct | — 20:09 | No data | — |
| Wed 14 Oct | Kampen Zuid 20:09Partial coverage | 0 min | — |
| Tue 13 Oct | Leeuwarden 20:10 | No data | — |
| Mon 12 Oct | Grou-Jirnsum 20:09 | No data | — |
| Sun 11 Oct | Dronten 20:10Partial coverage | 0 min | — |
| Sat 10 Oct | Dronten 20:10Partial coverage | 0 min | — |
| Fri 9 Oct | Leeuwarden 20:09Partial coverage | 0 min | — |
| Thu 8 Oct | — 20:09 | 0 min | — |
| Wed 7 Oct | — 20:12 | +2 min | +3 min |