Train NS 9063 Lelystad Centrum – Leeuwarden

Lelystad Centrum 17:52 → Leeuwarden 19:27 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:52 from Lelystad Centrum · Thu 5 Nov

Next departure 17:52 today · Lelystad Centrum
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 3 full · 13 partial · 13 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 3 full · 15 partial · 68 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: +1 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

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 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=1
  • 100% T n=3
  • 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, 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.

StopSched.Usually 9 days in 10
17:52on time on time
18:04— —
18:13— —
18:23 / 18:27— —
18:42— —
18:51— —
18:59— —
19:06— —
19:13— —
19:17— —
19:27— —

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 NovDronten 19:29No data—
Tue 3 NovDronten 19:29Partial coverage0 min—
Mon 2 NovDronten 18:18No data—
Sun 1 NovGrou-Jirnsum 19:33Partial coverage+1 min+1 min
Sat 31 OctHeerenveen 19:51Partial coverage0 min+13 min
Fri 30 OctSteenwijk 19:29No data—
Thu 29 OctLelystad Centrum 19:14Partial coverage0 min—
Wed 28 OctDronten 19:28No data—
Tue 27 OctDronten 19:31No data—
Mon 26 OctDronten 19:41Partial coverage0 min—
Sun 25 OctKampen Zuid 18:28No data—
Sat 24 OctKampen Zuid 18:280 min—
Fri 23 OctGrou-Jirnsum 19:31Partial coverage0 min—
Thu 22 OctMeppel 19:29Partial coverage0 min—
Wed 21 OctDronten 19:29No data—
Tue 20 OctMeppel 18:50Partial coverage0 min—
Mon 19 OctMeppel 19:30No data—
Sun 18 OctGrou-Jirnsum 19:32Partial coverage+1 min—
Sat 17 OctGrou-Jirnsum 19:32No data—
Fri 16 OctGrou-Jirnsum 19:31No data—
Thu 15 OctDronten 19:31No data—
Wed 14 OctGrou-Jirnsum 19:37No data—
Tue 13 OctDronten 19:29No data—
Mon 12 OctMeppel 19:290 min—
Sun 11 OctGrou-Jirnsum 19:31Partial coverage0 min—
Sat 10 OctGrou-Jirnsum 19:33Partial coverage+1 min—
Fri 9 OctDronten 19:29Partial coverage0 min—
Thu 8 OctLelystad Centrum 19:29+1 min—
Wed 7 OctDronten 19:28Partial coverage0 min—
Tue 6 OctDronten 19:29Partial coverage0 min—