Train NS 9025 Lelystad Centrum – Leeuwarden

Lelystad Centrum 08:22 → Leeuwarden 09:57 Mon, Tue, Wed, Thu, Fri, Sat 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 08:22 from Lelystad Centrum · Fri 20 Nov

Next departure 08:22 today · Lelystad Centrum
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 4 full · 14 partial · 7 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 6 full · 22 partial · 48 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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:22on time on time
08:35≈ on time ≈ on time
08:43≈ on time ≈ on time
08:53 / 08:57≈ on time ≈ on time
09:12≈ on time ≈ on time
09:21≈ on time ≈ on time
09:29≈ on time ≈ on time
09:36≈ on time ≈ on time
09:43≈ on time ≈ on time
09:47≈ on time ≈ on time
09:57on 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 19 NovGrou-Jirnsum 09:59Partial coverage0 min—
Wed 18 NovGrou-Jirnsum 10:02Partial coverage0 min—
Tue 17 NovGrou-Jirnsum 10:02Partial coverage+1 min—
Mon 16 NovGrou-Jirnsum 10:02Partial coverage0 min—
Sat 14 NovKampen Zuid 08:580 min—
Fri 13 NovGrou-Jirnsum 10:02Partial coverage+1 min+1 min
Thu 12 NovGrou-Jirnsum 10:02Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 09:59Partial coverage0 min—
Tue 10 NovGrou-Jirnsum 10:02Partial coverage0 min—
Mon 9 NovGrou-Jirnsum 10:02Partial coverage0 min—
Sat 7 NovKampen Zuid 08:580 min—
Fri 6 NovGrou-Jirnsum 09:59No data—
Thu 5 NovGrou-Jirnsum 09:59No data—
Wed 4 NovGrou-Jirnsum 10:02Partial coverage0 min—
Tue 3 NovGrou-Jirnsum 10:04No data—
Mon 2 NovGrou-Jirnsum 10:03Partial coverage0 min—
Sat 31 OctKampen Zuid 08:580 min—
Fri 30 OctGrou-Jirnsum 10:03Partial coverage0 min—
Thu 29 OctGrou-Jirnsum 10:02No data—
Wed 28 OctGrou-Jirnsum 10:02No data—
Tue 27 OctGrou-Jirnsum 10:02Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 10:02No data—
Sat 24 OctKampen Zuid 08:590 min—
Fri 23 OctGrou-Jirnsum 10:01No data—
Thu 22 OctGrou-Jirnsum 10:02Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 10:01No data—
Tue 20 OctGrou-Jirnsum 10:02Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 10:02Partial coverage0 min—
Sat 17 OctKampen Zuid 08:580 min—
Fri 16 OctGrou-Jirnsum 10:02Partial coverage0 min—