Train NS 9027 Lelystad Centrum – Leeuwarden

Lelystad Centrum 08:52 → Leeuwarden 10:27 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 08:52 from Lelystad Centrum · Sat 7 Nov

Next departure 08:52 today · Lelystad Centrum
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 67 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 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
08:52on time on time
09:05— —
09:13— —
09:23 / 09:27— —
09:42— —
09:51— —
09:59— —
10:06— —
10:13— —
10:17— —
10:27— —

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
Fri 6 NovGrou-Jirnsum 10:29No data—
Thu 5 NovGrou-Jirnsum 10:34No data—
Wed 4 NovGrou-Jirnsum 10:32Partial coverage+1 min—
Tue 3 NovGrou-Jirnsum 10:32No data—
Mon 2 NovGrou-Jirnsum 10:29No data—
Sun 1 NovGrou-Jirnsum 10:37Partial coverage+4 min+5 min
Sat 31 OctGrou-Jirnsum 10:31Partial coverage+1 min—
Fri 30 OctGrou-Jirnsum 10:31Partial coverage0 min—
Thu 29 OctGrou-Jirnsum 10:32No data—
Wed 28 OctGrou-Jirnsum 10:34Partial coverage0 min—
Tue 27 OctGrou-Jirnsum 10:31Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 10:32No data—
Sun 25 OctKampen Zuid 09:34No data—
Sat 24 OctKampen Zuid 09:280 min—
Fri 23 OctGrou-Jirnsum 10:31No data—
Thu 22 OctGrou-Jirnsum 10:32Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 10:32No data—
Tue 20 OctGrou-Jirnsum 10:31Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 10:32No data—
Sun 18 OctGrou-Jirnsum 10:32Partial coverage0 min—
Sat 17 OctGrou-Jirnsum 10:31Partial coverage0 min—
Fri 16 OctGrou-Jirnsum 10:32No data—
Thu 15 OctZwolle 10:58No data—
Wed 14 OctGrou-Jirnsum 10:31No data—
Tue 13 OctGrou-Jirnsum 10:31Partial coverage0 min—
Mon 12 OctGrou-Jirnsum 10:320 min—
Sun 11 OctGrou-Jirnsum 10:32Partial coverage+1 min—
Sat 10 OctGrou-Jirnsum 10:32Partial coverage+1 min—
Fri 9 OctGrou-Jirnsum 10:350 min—
Thu 8 OctGrou-Jirnsum 10:31Partial coverage0 min—