Train NS 9047 Lelystad Centrum – Leeuwarden

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

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

Next departure 13:52 today · Lelystad Centrum
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 2 full · 17 partial · 10 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 5 full · 27 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Mon 5 Oct Max en route +4 min · last fix heading to Grou-Jirnsum +4 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +4 min

Distribution · 90 days

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

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

On-time by weekday

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