Train NS 9054 Leeuwarden – Lelystad Centrum

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

✓ Today’s run finished

Today, last fix heading to Dronten at 16:19 0 min

  1. Leeuwarden14:33
  2. Akkrum14:46
  3. Heerenveen14:53
  4. Steenwijk15:08
  5. Zwolle15:32
  6. Dronten15:55
  7. Lelystad Centrum16:08

Next service: tomorrow 14:33 from Leeuwarden · Tue 17 Nov

Next departure 14:33 tomorrow · Leeuwarden
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 1 full · 16 partial · 13 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 2 full · 23 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 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, 25 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
14:33on time on time
14:42— —
14:46— —
14:53— —
15:00— —
15:08— —
15:17— —
15:32 / 15:37— —
15:47— —
15:55— —
16:08— —

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 NovDronten 16:19Partial coverage0 min—
Sun 15 NovDronten 16:09Partial coverage0 min—
Sat 14 NovDronten 16:09Partial coverage0 min—
Fri 13 NovDronten 16:09Partial coverage0 min—
Thu 12 NovDronten 16:09Partial coverage0 min—
Wed 11 NovDronten 16:09Partial coverage0 min—
Tue 10 NovDronten 16:09Partial coverage0 min—
Mon 9 NovDronten 16:22Partial coverage0 min—
Sun 8 NovDronten 16:09Partial coverage0 min—
Sat 7 NovDronten 16:09Partial coverage0 min—
Fri 6 NovDronten 16:09No data—
Thu 5 NovDronten 16:10No data—
Wed 4 NovDronten 16:09Partial coverage0 min—
Tue 3 NovDronten 16:09No data—
Mon 2 NovDronten 16:09No data—
Sun 1 NovDronten 16:10Partial coverage0 min—
Sat 31 OctDronten 16:09Partial coverage0 min—
Fri 30 OctDronten 16:10No data—
Thu 29 OctDronten 16:10No data—
Wed 28 OctDronten 16:09No data—
Tue 27 OctDronten 16:14Partial coverage0 min—
Mon 26 OctDronten 16:09No data—
Sun 25 OctDronten 16:09No data—
Sat 24 OctDronten 16:090 min—
Fri 23 OctDronten 16:19No data—
Thu 22 OctDronten 16:09No data—
Wed 21 OctDronten 16:10No data—
Tue 20 OctDronten 16:09Partial coverage0 min—
Mon 19 OctDronten 16:11No data—
Sun 18 OctDronten 16:09Partial coverage0 min—