Train NS 9049 Lelystad Centrum – Leeuwarden

Lelystad Centrum 14:22 → Leeuwarden 15:57 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Grou-Jirnsum at 16:04 0 min

  1. Lelystad Centrum14:22
  2. Kampen Zuid14:43
  3. Zwolle14:53
  4. Steenwijk15:21
  5. Heerenveen15:36
  6. Grou-Jirnsum15:47
  7. Leeuwarden15:57

Next service: tomorrow 14:22 from Lelystad Centrum · Tue 17 Nov

Next departure 14:22 tomorrow · Lelystad Centrum
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 10 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 12 full · 18 partial · 58 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: 0 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 +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

  • 83% M n=6
  • 100% T n=5
  • 100% W n=3
  • 100% T n=3
  • 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, 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 10
14:22on time on time
14:34≈ on time ≈ on time
14:43≈ on time ≈ on time
14:53 / 14:57≈ on time ≈ on time
15:12≈ on time ≈ +1 min
15:21≈ on time ≈ +1 min
15:29≈ on time ≈ +1 min
15:36≈ on time ≈ +1 min
15:43≈ on time ≈ +1 min
15:47≈ on time ≈ +1 min
15:57on time +1 min

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 NovGrou-Jirnsum 16:04Partial coverage0 min+1 min
Sun 15 NovKampen Zuid 14:59+1 min+1 min
Sat 14 NovKampen Zuid 14:580 min—
Fri 13 NovGrou-Jirnsum 15:59Partial coverage0 min—
Thu 12 NovGrou-Jirnsum 16:02Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 15:59Partial coverage0 min—
Tue 10 NovGrou-Jirnsum 16:02Partial coverage0 min—
Mon 9 NovGrou-Jirnsum 15:59Partial coverage0 min—
Sun 8 NovKampen Zuid 14:590 min—
Sat 7 NovKampen Zuid 14:580 min—
Fri 6 NovGrou-Jirnsum 15:59No data—
Thu 5 NovGrou-Jirnsum 16:02No data—
Wed 4 NovGrou-Jirnsum 16:02Partial coverage0 min—
Tue 3 NovGrou-Jirnsum 16:02No data—
Mon 2 NovGrou-Jirnsum 16:02Partial coverage0 min—
Sun 1 NovKampen Zuid 14:590 min—
Sat 31 OctKampen Zuid 14:590 min—
Fri 30 OctGrou-Jirnsum 16:02No data—
Thu 29 OctGrou-Jirnsum 16:16No data—
Wed 28 OctGrou-Jirnsum 16:01No data—
Tue 27 OctGrou-Jirnsum 16:040 min—
Mon 26 OctGrou-Jirnsum 16:01No data—
Sun 25 OctKampen Zuid 14:58No data—
Sat 24 OctKampen Zuid 14:580 min—
Fri 23 OctGrou-Jirnsum 16:02No data—
Thu 22 OctGrou-Jirnsum 16:02Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 16:03No data—
Tue 20 OctGrou-Jirnsum 16:01Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 16:08Partial coverage0 min—
Sun 18 OctKampen Zuid 14:580 min—