Train NS 9046 Leeuwarden – Lelystad Centrum

Leeuwarden 12:33 → Lelystad Centrum 14:08 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 12:33 from Leeuwarden · Fri 6 Nov

Next departure 12:33 today · Leeuwarden
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 1 full · 15 partial · 13 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 2 full · 17 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Lelystad Centrum, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:33on time on time
12:42— —
12:46— —
12:53— —
13:00— —
13:08— —
13:17— —
13:32 / 13:37— —
13:47— —
13:55— —
14:08— —

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 NovDronten 14:09No data—
Wed 4 NovDronten 14:09Partial coverage0 min—
Tue 3 NovDronten 14:09No data—
Mon 2 NovDronten 14:09Partial coverage0 min—
Sun 1 NovDronten 14:11Partial coverage0 min—
Sat 31 OctDronten 14:11Partial coverage0 min+2 min
Fri 30 OctDronten 14:09No data—
Thu 29 OctDronten 14:11Partial coverage0 min—
Wed 28 OctDronten 14:10No data—
Tue 27 OctDronten 14:10No data—
Mon 26 OctDronten 14:10No data—
Sun 25 OctDronten 14:09No data—
Sat 24 OctDronten 14:090 min—
Fri 23 OctDronten 14:09No data—
Thu 22 OctDronten 14:09Partial coverage0 min—
Wed 21 OctDronten 14:09No data—
Tue 20 OctDronten 14:09Partial coverage0 min—
Mon 19 OctDronten 14:10No data—
Sun 18 OctDronten 14:10Partial coverage0 min—
Sat 17 OctDronten 14:09Partial coverage0 min—
Fri 16 OctDronten 14:10Partial coverage0 min—
Thu 15 OctDronten 14:10No data—
Wed 14 OctDronten 14:09No data—
Tue 13 OctDronten 14:50Partial coverage0 min—
Mon 12 OctDronten 14:10No data—
Sun 11 OctDronten 14:09Partial coverage0 min—
Sat 10 OctDronten 14:10Partial coverage0 min—
Fri 9 OctDronten 14:10Partial coverage+2 min+2 min
Thu 8 OctDronten 14:09Partial coverage0 min—
Wed 7 OctDronten 14:10Partial coverage0 min—