Train NS 9056 Leeuwarden – Lelystad Centrum

Leeuwarden 15:03 → Lelystad Centrum 16:37 Daily 1 h 34 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 15:03 from Leeuwarden · Thu 19 Nov

Next departure 15:03 today · Leeuwarden
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 11 full · 9 partial · 9 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 18 full · 15 partial · 52 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: +2 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

  • Wed 11 Nov Max en route +16 min · last fix heading to Dronten +16 min
  • Tue 10 Nov Max en route +13 min · last fix heading to Dronten +11 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Dronten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 86% T n=7
  • 80% W n=5
  • 100% T n=2
  • 100% F n=3
  • 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, 33 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
15:03on time on time
15:12≈ on time ≈ on time
15:16≈ on time ≈ on time
15:23≈ on time ≈ on time
15:30≈ on time ≈ on time
15:38≈ on time ≈ on time
15:47≈ on time ≈ on time
16:02 / 16:07≈ on time ≈ on time
16:17≈ on time ≈ on time
16:25≈ on time ≈ on time
16:37on 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

DateLast stopFinalMax
Wed 18 NovDronten 16:39Partial coverage0 min—
Tue 17 NovDronten 16:390 min—
Mon 16 NovDronten 16:40Partial coverage0 min—
Sun 15 NovDronten 16:390 min—
Sat 14 NovDronten 16:390 min—
Fri 13 NovDronten 16:39Partial coverage0 min—
Thu 12 NovDronten 16:39Partial coverage0 min—
Wed 11 NovDronten 16:54Partial coverage+16 min+16 min
Tue 10 NovDronten 16:59+11 min+13 min
Mon 9 NovDronten 16:39Partial coverage0 min—
Sun 8 NovDronten 16:400 min—
Sat 7 NovDronten 16:390 min—
Fri 6 NovDronten 16:39No data—
Thu 5 NovDronten 16:39No data—
Wed 4 NovDronten 16:39Partial coverage0 min—
Tue 3 NovDronten 16:390 min—
Mon 2 NovDronten 16:39Partial coverage0 min—
Sun 1 NovDronten 16:42+1 min—
Sat 31 OctDronten 16:390 min—
Fri 30 OctDronten 16:39No data—
Thu 29 OctDronten 16:39No data—
Wed 28 OctDronten 16:39No data—
Tue 27 OctDronten 16:390 min—
Mon 26 OctDronten 16:39No data—
Sun 25 OctDronten 16:40No data—
Sat 24 OctDronten 16:390 min—
Fri 23 OctDronten 16:41Partial coverage0 min—
Thu 22 OctDronten 16:41No data—
Wed 21 OctDronten 16:39No data—
Tue 20 OctDronten 16:400 min—