Train NS 9076 Leeuwarden – Lelystad Centrum

Leeuwarden 20:03 → Lelystad Centrum 21:38 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 21:39 No data

  1. Leeuwarden20:03
  2. Akkrum20:16
  3. Heerenveen20:23
  4. Steenwijk20:38
  5. Zwolle21:02
  6. Kampen Zuid21:17
  7. Lelystad Centrum21:38

Next service: tomorrow 20:03 from Leeuwarden · Fri 6 Nov

Full trip card
Next departure 20:03 tomorrow · Leeuwarden
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 27 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 23 Oct Max en route +20 min · last fix heading to — +18 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
Leeuwarden
20:03on time on time
Grou-Jirnsum
20:12≈ on time ≈ on time
Akkrum
20:16≈ on time ≈ on time
Heerenveen
20:23≈ on time ≈ on time
Wolvega
20:30≈ on time ≈ on time
Steenwijk
20:38≈ on time ≈ on time
Meppel
20:47≈ on time ≈ on time
Zwolle
21:02 / 21:07≈ on time ≈ on time
Kampen Zuid
21:17≈ on time ≈ on time
Dronten
21:25≈ on time ≈ on time
Lelystad Centrum
21:38on 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
Thu 5 Nov— 21:39No data—
Wed 4 Nov— 21:390 min—
Tue 3 Nov— 21:03No data—
Mon 2 Nov— 21:03No data—
Sun 1 NovDronten 21:390 min—
Sat 31 OctDronten 21:39No data—
Fri 30 Oct— 21:390 min—
Thu 29 Oct— 21:390 min—
Wed 28 Oct— 21:39No data—
Tue 27 Oct— 21:40No data—
Mon 26 Oct— 21:390 min—
Sun 25 OctDronten 21:40No data—
Sat 24 OctDronten 21:400 min—
Fri 23 Oct— 22:02+18 min+20 min
Thu 22 Oct— 21:400 min—
Wed 21 Oct— 21:39No data—
Tue 20 Oct— 21:390 min—
Sun 18 OctDronten 21:400 min—
Sat 17 OctDronten 21:42No data—
Fri 16 Oct— 21:390 min—
Thu 15 Oct— 21:390 min—
Wed 14 Oct— 21:390 min—
Tue 13 Oct— 21:390 min—
Mon 12 Oct— 22:040 min—
Sat 10 OctDronten 21:400 min—
Fri 9 Oct— 21:390 min—
Thu 8 Oct— 21:390 min—
Wed 7 Oct— 21:030 min—
Tue 6 Oct— 21:390 min—
Mon 5 Oct— 21:44+1 min+1 min