Train NS 9082 Leeuwarden – Lelystad Centrum

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:33 from Leeuwarden · Thu 5 Nov

Next departure 21:33 today · Leeuwarden
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 7 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 25 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: +1 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 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 75% F n=4
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 22 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
21:33on time on time
21:42≈ on time ≈ on time
21:46≈ on time ≈ on time
21:53≈ on time ≈ on time
22:00≈ on time ≈ on time
22:08≈ on time ≈ on time
22:17≈ on time ≈ on time
22:32 / 22:37≈ on time ≈ on time
22:47≈ on time ≈ on time
22:55≈ on time ≈ on time
23:08on time +1 min

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 4 Nov— 23:090 min—
Mon 2 Nov— 23:09+1 min—
Sun 1 NovDronten 23:09+1 min+1 min
Sat 31 OctDronten 23:09No data—
Fri 30 Oct— 23:090 min—
Thu 29 Oct— 23:090 min—
Wed 28 Oct— 23:100 min—
Tue 27 Oct— 23:090 min—
Mon 26 Oct— 23:09No data—
Sun 25 OctDronten 23:14No data—
Sat 24 OctZwolle 23:090 min—
Fri 23 Oct— 23:100 min—
Thu 22 Oct— 23:10No data—
Wed 21 Oct— 23:09No data—
Mon 19 Oct— 22:220 min—
Sun 18 OctDronten 23:090 min—
Sat 17 OctDronten 23:09No data—
Fri 16 Oct— 23:090 min—
Thu 15 Oct— 23:11No data—
Wed 14 Oct— 23:090 min—
Tue 13 Oct— 23:190 min—
Mon 12 Oct— 23:090 min—
Sun 11 OctMeppel 22:330 min—
Sat 10 OctWolvega 23:100 min—
Fri 9 Oct— 23:10+3 min+3 min
Thu 8 Oct— 23:090 min—
Wed 7 Oct— 23:090 min—
Tue 6 Oct— 23:080 min—
Mon 5 Oct— 23:090 min—
Sun 4 OctDronten 23:10No data—