Train NS 9058 Leeuwarden – Lelystad Centrum

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 15:33 from Leeuwarden · Tue 17 Nov

Next departure 15:33 today · Leeuwarden
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 1 full · 19 partial · 9 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 2 full · 29 partial · 57 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: 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

  • Sat 31 Oct Max en route +12 min · last fix heading to Dronten +11 min

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

On-time by weekday

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