Train NS 9086 Leeuwarden – Lelystad Centrum

Leeuwarden 22:33 → Lelystad Centrum 00: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 22:33 from Leeuwarden · Tue 17 Nov

Next departure 22:33 today · Leeuwarden
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 25 full · 2 partial · 2 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 38 full · 3 partial · 15 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

  • Fri 6 Nov Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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