Train NS 9069 Lelystad Centrum – Leeuwarden

Lelystad Centrum 19:22 → Leeuwarden 20:57 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 19:22 from Lelystad Centrum · Thu 5 Nov

Next departure 19:22 today · Lelystad Centrum
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 19 full · 1 partial · 9 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Leeuwarden, 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 +19 min · last fix heading to — +18 min
  • Thu 8 Oct Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=2
  • 33% T n=3
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 stops).

Last 90 days, 22 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
19:22on time on time
19:34≈ on time ≈ on time
19:43≈ on time ≈ on time
19:53 / 19:57≈ on time ≈ on time
20:12≈ on time ≈ on time
20:21≈ on time ≈ on time
20:29≈ on time ≈ on time
20:36≈ on time ≈ +1 min
20:43≈ on time ≈ +1 min
20:47≈ on time ≈ +1 min
20:57on time +1 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
Wed 4 Nov— 20:59+1 min—
Tue 3 Nov— 20:58No data—
Mon 2 Nov— 20:59No data—
Sun 1 NovKampen Zuid 19:590 min—
Sat 31 OctKampen Zuid 19:590 min—
Fri 30 Oct— 20:590 min—
Thu 29 Oct— 21:34+18 min+19 min
Wed 28 Oct— 20:58No data—
Tue 27 Oct— 21:000 min—
Mon 26 OctKampen Zuid 21:04No data—
Sun 25 OctKampen Zuid 19:58No data—
Sat 24 OctKampen Zuid 20:040 min—
Fri 23 OctLelystad Centrum 21:03Partial coverage+3 min+3 min
Thu 22 Oct— 21:000 min—
Wed 21 Oct— 21:03No data—
Tue 20 Oct— 20:590 min—
Mon 19 Oct— 21:01No data—
Sun 18 OctKampen Zuid 19:580 min—
Sat 17 OctKampen Zuid 19:580 min—
Fri 16 OctDronten 20:580 min—
Thu 15 Oct— 20:58No data—
Wed 14 OctDronten 20:59No data—
Tue 13 Oct— 20:590 min—
Mon 12 Oct— 20:380 min—
Sun 11 OctKampen Zuid 19:580 min—
Sat 10 OctKampen Zuid 19:590 min—
Fri 9 Oct— 21:00+1 min+1 min
Thu 8 Oct— 21:11+9 min+9 min
Wed 7 Oct— 20:580 min—
Tue 6 Oct— 20:580 min—