Train NS 9071 Lelystad Centrum – Leeuwarden

Lelystad Centrum 19:52 → Leeuwarden 21:27 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 19:52 from Lelystad Centrum · Tue 17 Nov

Next departure 19:52 today · Lelystad Centrum
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 31 full · 1 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Leeuwarden, 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 6 Oct Max en route +8 min · last fix heading to — +7 min
  • Sat 14 Nov Max en route +6 min · last fix heading to Grou-Jirnsum +6 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Grou-Jirnsum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 100% W n=4
  • 100% T n=3
  • 100% F n=5
  • 75% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 32 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:52on time on time
20:04≈ on time ≈ on time
20:13≈ on time ≈ on time
20:23 / 20:27≈ on time ≈ +1 min
20:42≈ on time ≈ +1 min
20:51≈ on time ≈ +1 min
20:59≈ on time ≈ +1 min
21:06≈ on time ≈ +2 min
21:13≈ on time ≈ +2 min
21:17≈ on time ≈ +2 min
21:27on time +2 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
Mon 16 Nov— 21:290 min+2 min
Sun 15 NovGrou-Jirnsum 21:290 min—
Sat 14 NovGrou-Jirnsum 21:37+6 min+6 min
Fri 13 Nov— 21:29+2 min+4 min
Thu 12 Nov— 21:29+2 min+3 min
Wed 11 Nov— 21:280 min—
Tue 10 Nov— 21:29+1 min—
Mon 9 Nov— 20:140 min—
Sun 8 NovGrou-Jirnsum 21:34+4 min+4 min
Sat 7 NovGrou-Jirnsum 21:320 min—
Fri 6 Nov— 21:290 min—
Thu 5 Nov— 21:29No data—
Wed 4 Nov— 21:290 min+2 min
Mon 2 Nov— 21:290 min—
Sun 1 NovGrou-Jirnsum 21:32+1 min—
Sat 31 OctGrou-Jirnsum 21:32No data—
Fri 30 Oct— 20:49No data—
Thu 29 Oct— 21:140 min—
Wed 28 Oct— 21:29No data—
Tue 27 Oct— 21:290 min—
Mon 26 Oct— 21:29No data—
Sun 25 OctKampen Zuid 20:28No data—
Sat 24 OctKampen Zuid 20:280 min—
Fri 23 Oct— 21:30+1 min+2 min
Thu 22 Oct— 21:30No data—
Wed 21 Oct— 21:29No data—
Tue 20 Oct— 21:310 min—
Mon 19 Oct— 21:280 min—
Sun 18 OctGrou-Jirnsum 21:32+1 min—
Sat 17 OctGrou-Jirnsum 21:31No data—