Train NS 9050 Leeuwarden – Lelystad Centrum

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

✓ Today’s run finished

Today, last fix heading to Dronten at 15:10 0 min

  1. Leeuwarden13:33
  2. Akkrum13:46
  3. Heerenveen13:53
  4. Steenwijk14:09
  5. Zwolle14:32
  6. Dronten14:55
  7. Lelystad Centrum15:08

Next service: tomorrow 13:33 from Leeuwarden · Tue 17 Nov

Next departure 13:33 tomorrow · Leeuwarden
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 1 full · 17 partial · 12 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 3 full · 26 partial · 60 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

Worst days

  • Tue 10 Nov Max en route +3 min · last fix heading to Dronten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 100% W n=4
  • 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, 29 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:33on time on time
13:42— —
13:46— —
13:53— —
14:00— —
14:09— —
14:17— —
14:32 / 14:37— —
14:47— —
14:55— —
15: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
Mon 16 NovDronten 15:10Partial coverage0 min—
Sun 15 NovDronten 15:09Partial coverage0 min—
Sat 14 NovDronten 15:09Partial coverage0 min—
Fri 13 NovDronten 15:09Partial coverage0 min—
Thu 12 NovDronten 15:09Partial coverage0 min—
Wed 11 NovDronten 15:09Partial coverage0 min—
Tue 10 NovDronten 15:09Partial coverage+3 min+3 min
Mon 9 NovDronten 15:09Partial coverage0 min—
Sun 8 NovDronten 15:09Partial coverage0 min—
Sat 7 NovDronten 15:09Partial coverage0 min—
Fri 6 NovDronten 15:09No data—
Thu 5 NovDronten 15:19No data—
Wed 4 NovDronten 15:09Partial coverage0 min—
Tue 3 NovDronten 15:09No data—
Mon 2 NovDronten 15:09No data—
Sun 1 NovDronten 15:10Partial coverage0 min—
Sat 31 OctDronten 15:09Partial coverage0 min—
Fri 30 OctDronten 15:09No data—
Thu 29 OctDronten 15:10No data—
Wed 28 OctDronten 15:09No data—
Tue 27 OctDronten 15:10Partial coverage0 min—
Mon 26 OctDronten 15:09No data—
Sun 25 OctDronten 15:09No data—
Sat 24 OctDronten 15:100 min—
Fri 23 OctDronten 15:09No data—
Thu 22 OctDronten 15:09Partial coverage0 min—
Wed 21 OctDronten 15:09No data—
Tue 20 OctDronten 15:10Partial coverage0 min—
Mon 19 OctDronten 15:10No data—
Sun 18 OctDronten 15:10Partial coverage0 min+1 min