Train NS 9026 Leeuwarden – Lelystad Centrum

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

✓ Today’s run finished

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

  1. Leeuwarden07:33
  2. Akkrum07:46
  3. Heerenveen07:53
  4. Steenwijk08:08
  5. Zwolle08:32
  6. Dronten08:55
  7. Lelystad Centrum09:07

Next service: tomorrow 07:33 from Leeuwarden · Thu 19 Nov

Next departure 07:33 tomorrow · Leeuwarden
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 1 full · 21 partial · 8 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 1 full · 30 partial · 58 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

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

  • Early 0% · 0
  • On time 100% · 31
  • 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=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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
07:33on time on time
07:42— —
07:46— —
07:53— —
08:00— —
08:08— —
08:17— —
08:32 / 08:37— —
08:47— —
08:55— —
09:07— —

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