Train NS 9043 Lelystad Centrum – Leeuwarden

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

It has not run yet today

Last recorded run: Tuesday 17 November +7 min

Next service: today 12:52 from Lelystad Centrum · Wed 18 Nov

Next departure 12:52 today · Lelystad Centrum
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 1 full · 16 partial · 12 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 2 full · 24 partial · 60 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

  • Tue 17 Nov Max en route +8 min · last fix heading to Grou-Jirnsum +7 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Grou-Jirnsum +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 80% T n=5
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 26 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
12:52on time on time
13:05— —
13:13— —
13:23 / 13:27— —
13:42— —
13:51— —
13:59— —
14:06— —
14:13— —
14:17— —
14: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
Tue 17 NovGrou-Jirnsum 14:39Partial coverage+7 min+8 min
Mon 16 NovGrou-Jirnsum 14:33Partial coverage0 min—
Sun 15 NovGrou-Jirnsum 14:33Partial coverage+1 min+2 min
Sat 14 NovGrou-Jirnsum 14:32Partial coverage0 min—
Fri 13 NovGrou-Jirnsum 14:32Partial coverage+1 min—
Thu 12 NovGrou-Jirnsum 14:29Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 14:32Partial coverage0 min—
Tue 10 NovGrou-Jirnsum 14:32Partial coverage+1 min—
Mon 9 NovGrou-Jirnsum 14:29Partial coverage0 min—
Sun 8 NovGrou-Jirnsum 14:33Partial coverage+1 min—
Sat 7 NovGrou-Jirnsum 14:29Partial coverage0 min—
Fri 6 NovGrou-Jirnsum 14:32No data—
Thu 5 NovGrou-Jirnsum 14:29No data—
Wed 4 NovGrou-Jirnsum 14:33Partial coverage0 min+2 min
Tue 3 NovGrou-Jirnsum 14:29No data—
Mon 2 NovGrou-Jirnsum 14:32No data—
Sun 1 NovGrou-Jirnsum 14:32Partial coverage0 min—
Sat 31 OctGrou-Jirnsum 14:32Partial coverage+1 min—
Fri 30 OctGrou-Jirnsum 14:34No data—
Thu 29 OctGrou-Jirnsum 14:31No data—
Wed 28 OctGrou-Jirnsum 14:32No data—
Tue 27 OctGrou-Jirnsum 14:34Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 14:31No data—
Sun 25 OctKampen Zuid 13:28No data—
Sat 24 OctKampen Zuid 13:280 min—
Fri 23 OctGrou-Jirnsum 14:36No data—
Thu 22 OctGrou-Jirnsum 14:33No data—
Wed 21 OctGrou-Jirnsum 14:32No data—
Tue 20 OctGrou-Jirnsum 14:33Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 14:31Partial coverage0 min—