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: Wednesday 18 November 0 min

Next service: today 08:52 from Lelystad Centrum · Thu 19 Nov

Next departure 08:52 today · Lelystad Centrum
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 2 full · 18 partial · 9 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 5 full · 26 partial · 55 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: +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 17 Nov Max en route +7 min · last fix heading to Grou-Jirnsum +6 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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≈ on time ≈ on time
09:13≈ on time ≈ on time
09:23 / 09:27≈ on time ≈ on time
09:42≈ on time ≈ on time
09:51≈ on time ≈ +1 min
09:59≈ on time ≈ +1 min
10:06≈ on time ≈ +1 min
10:13≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:27on 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 18 NovGrou-Jirnsum 10:29Partial coverage0 min—
Tue 17 NovGrou-Jirnsum 10:38Partial coverage+6 min+7 min
Mon 16 NovGrou-Jirnsum 10:32Partial coverage0 min—
Sun 15 NovGrou-Jirnsum 10:33Partial coverage+1 min+1 min
Sat 14 NovGrou-Jirnsum 10:34Partial coverage+2 min+3 min
Fri 13 NovGrou-Jirnsum 10:32Partial coverage0 min—
Thu 12 NovGrou-Jirnsum 10:32Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 10:32Partial coverage+1 min+1 min
Tue 10 NovGrou-Jirnsum 10:32Partial coverage0 min—
Mon 9 NovGrou-Jirnsum 10:290 min—
Sun 8 NovGrou-Jirnsum 10:32Partial coverage0 min—
Sat 7 NovGrou-Jirnsum 10:29Partial coverage0 min—
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—