Train NS 9053 Lelystad Centrum – Leeuwarden

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:22 from Lelystad Centrum · Thu 5 Nov

Next departure 15:22 today · Lelystad Centrum
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 11 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 12 full · 8 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 9 Oct Max en route +6 min · last fix heading to Grou-Jirnsum +6 min

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 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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