Train NS 9074 Leeuwarden – Lelystad Centrum

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 19:33 from Leeuwarden · Mon 16 Nov

Next departure 19:33 today · Leeuwarden
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 14 full · 6 partial · 6 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 22 full · 8 partial · 24 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

  • Tue 10 Nov Max en route +13 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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