Train NS 9070 Leeuwarden – Lelystad Centrum

Leeuwarden 18:33 → Lelystad Centrum 20:08 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 18:33 from Leeuwarden · Tue 17 Nov

Next departure 18:33 today · Leeuwarden
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 9 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 14 full · 14 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

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

28 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 67% T n=3
  • 100% F n=4
  • 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, 28 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.

StopSched.Usually 9 days in 10
18:33on 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 ≈ +2 min
19:32 / 19:37≈ on time ≈ +2 min
19:47≈ on time ≈ +1 min
19:55≈ on time ≈ +1 min
20:08on 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

DateLast stopFinalMax
Mon 16 Nov— 20:320 min+18 min
Sun 15 NovDronten 20:09Partial coverage0 min—
Sat 14 NovDronten 20:09Partial coverage0 min—
Fri 13 NovHeerenveen 20:09Partial coverage0 min—
Thu 12 Nov— 20:090 min—
Wed 11 Nov— 20:090 min—
Tue 10 Nov— 18:490 min—
Mon 9 Nov— 19:340 min—
Sun 8 NovDronten 20:09Partial coverage0 min—
Sat 7 NovDronten 20:09Partial coverage0 min—
Fri 6 NovAkkrum 20:09Partial coverage0 min—
Thu 5 Nov— 20:09No data—
Wed 4 Nov— 20:090 min—
Tue 3 Nov— 20:09No data—
Sun 1 NovDronten 20:09Partial coverage0 min—
Sat 31 OctDronten 20:090 min—
Fri 30 OctHeerenveen 20:09No data—
Thu 29 Oct— 20:09+4 min+4 min
Wed 28 Oct— 20:09No data—
Tue 27 Oct— 20:09No data—
Mon 26 OctKampen Zuid 20:090 min—
Sun 25 OctDronten 20:09No data—
Sat 24 OctDronten 20:090 min—
Fri 23 OctMeppel 20:09Partial coverage0 min—
Thu 22 OctGrou-Jirnsum 20:10No data—
Wed 21 OctLeeuwarden 20:18No data—
Tue 20 OctAkkrum 20:16Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 20:10No data—
Sun 18 OctDronten 20:10Partial coverage0 min—
Sat 17 OctDronten 20:10No data—