Train NS 9045 Lelystad Centrum – Leeuwarden

Lelystad Centrum 13:22 → Leeuwarden 14:57 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:22 from Lelystad Centrum · Fri 6 Nov

Next departure 13:22 today · Lelystad Centrum
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 12 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 7 full · 13 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: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

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