Train NS 9031 Lelystad Centrum – Leeuwarden

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

Running now · updated 10:00

Heading to Leeuwarden 0 min

Estimated arrival at Leeuwarden 11:27 · 158 km/h

  1. Lelystad Centrum09:52
  2. Kampen Zuid10:13
  3. Zwolle10:23
  4. Steenwijk10:51
  5. Heerenveen11:06
  6. Akkrum11:13
  7. Leeuwarden11:27

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 20 runs arrived on time.

On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 2 full · 18 partial · 10 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 3 full · 27 partial · 57 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: +2 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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