Train NS 9048 Leeuwarden – Lelystad Centrum

Leeuwarden 13:03 → Lelystad Centrum 14:38 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dronten at 14:44 +3 min

  1. Leeuwarden13:03
  2. Akkrum13:16
  3. Heerenveen13:23
  4. Steenwijk13:38
  5. Zwolle14:02
  6. Dronten14:25
  7. Lelystad Centrum14:38

Next service: tomorrow 13:03 from Leeuwarden · Wed 18 Nov

Next departure 13:03 tomorrow · Leeuwarden
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 13 full · 11 partial · 6 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 19 full · 16 partial · 51 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 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

  • Wed 4 Nov Max en route +9 min · last fix heading to Dronten +9 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Dronten +4 min
  • Tue 17 Nov Max en route +3 min · last fix heading to Dronten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 50% T n=4
  • 83% W n=6
  • 100% T n=6
  • 100% F n=5
  • 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, 35 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:03on time on time
13:12≈ on time ≈ on time
13:16≈ on time ≈ on time
13:23≈ on time ≈ on time
13:30≈ on time ≈ on time
13:38≈ on time ≈ on time
13:47≈ on time ≈ on time
14:02 / 14:07≈ on time ≈ on time
14:17≈ on time ≈ on time
14:25≈ on time ≈ on time
14:38on 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 NovDronten 14:44Partial coverage+3 min+3 min
Mon 16 NovDronten 14:39Partial coverage0 min—
Sun 15 NovDronten 14:400 min—
Sat 14 NovDronten 14:390 min—
Fri 13 NovDronten 14:39Partial coverage0 min—
Thu 12 NovDronten 14:39+1 min+1 min
Wed 11 NovDronten 14:39Partial coverage0 min—
Tue 10 NovDronten 14:44Partial coverage0 min—
Mon 9 NovDronten 14:39Partial coverage0 min—
Sun 8 NovDronten 14:390 min—
Sat 7 NovDronten 14:390 min—
Fri 6 NovDronten 14:39No data—
Thu 5 NovDronten 14:490 min—
Wed 4 NovDronten 14:49Partial coverage+9 min+9 min
Tue 3 NovDronten 14:39No data—
Mon 2 NovDronten 14:39No data—
Sun 1 NovDronten 14:410 min—
Sat 31 OctDronten 14:400 min—
Fri 30 OctDronten 14:420 min—
Thu 29 OctDronten 14:420 min—
Wed 28 OctDronten 14:410 min—
Tue 27 OctDronten 14:44No data—
Mon 26 OctDronten 14:41No data—
Sun 25 OctDronten 14:39No data—
Sat 24 OctDronten 14:400 min—
Fri 23 OctDronten 14:42Partial coverage0 min—
Thu 22 OctDronten 14:390 min—
Wed 21 OctDronten 14:40Partial coverage0 min—
Tue 20 OctDronten 14:40Partial coverage0 min—
Mon 19 OctDronten 14:41Partial coverage0 min—