Train NS 9030 Leeuwarden – Lelystad Centrum

Leeuwarden 08:33 → Lelystad Centrum 10:07 Daily 1 h 34 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dronten at 10:09 0 min

  1. Leeuwarden08:33
  2. Akkrum08:46
  3. Heerenveen08:53
  4. Steenwijk09:08
  5. Zwolle09:32
  6. Dronten09:55
  7. Lelystad Centrum10:07

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

Next departure 08:33 tomorrow · Leeuwarden
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 5 full · 17 partial · 8 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 8 full · 25 partial · 56 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

Worst days

  • Sun 11 Oct Max en route +25 min · last fix heading to Kampen Zuid +25 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 97% · 32
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=3
  • 100% S n=6
  • 80% 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
08:33on time on time
08:42≈ on time ≈ on time
08:46≈ on time ≈ on time
08:53≈ on time ≈ on time
09:00≈ on time ≈ on time
09:08≈ on time ≈ on time
09:17≈ on time ≈ on time
09:32 / 09:37≈ on time ≈ on time
09:47≈ on time ≈ on time
09:55≈ on time ≈ on time
10:07on 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
Mon 16 NovDronten 10:09Partial coverage0 min—
Sun 15 NovDronten 10:09Partial coverage0 min—
Sat 14 NovDronten 10:090 min—
Fri 13 NovDronten 10:09Partial coverage0 min—
Thu 12 NovDronten 10:09Partial coverage0 min—
Wed 11 NovDronten 10:09Partial coverage0 min—
Tue 10 NovDronten 10:09Partial coverage0 min+1 min
Mon 9 NovDronten 10:09Partial coverage0 min—
Sun 8 NovDronten 10:09Partial coverage0 min—
Sat 7 NovDronten 10:090 min—
Fri 6 NovDronten 10:09No data—
Thu 5 NovDronten 10:09Partial coverage0 min—
Wed 4 NovDronten 10:09Partial coverage0 min—
Tue 3 NovDronten 10:19No data—
Mon 2 NovDronten 10:09No data—
Sun 1 NovDronten 10:09Partial coverage0 min—
Sat 31 OctDronten 10:090 min—
Fri 30 OctDronten 10:09No data—
Thu 29 OctDronten 10:15Partial coverage0 min—
Wed 28 OctDronten 10:10Partial coverage0 min—
Tue 27 OctDronten 10:100 min—
Mon 26 OctDronten 10:10No data—
Sun 25 OctDronten 10:09No data—
Sat 24 OctDronten 10:090 min—
Fri 23 OctDronten 10:10No data—
Thu 22 OctDronten 10:10Partial coverage0 min—
Wed 21 OctDronten 10:09No data—
Tue 20 OctDronten 10:16Partial coverage0 min—
Mon 19 OctDronten 10:09Partial coverage0 min—
Sun 18 OctDronten 10:20Partial coverage0 min—