Train NS 9057 Lelystad Centrum – Leeuwarden

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 16:22 from Lelystad Centrum · Fri 20 Nov

Next departure 16:22 today · Lelystad Centrum
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 8 full · 12 partial · 9 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 12 full · 19 partial · 56 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: +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

  • Fri 13 Nov Max en route +8 min · last fix heading to Grou-Jirnsum +7 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 100% W n=3
  • 100% T n=3
  • 75% F n=4
  • 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, 31 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
16:22on time on time
16:34≈ on time ≈ on time
16:43≈ on time ≈ on time
16:53 / 16:57≈ on time ≈ on time
17:12≈ on time ≈ on time
17:21≈ on time ≈ on time
17:29≈ on time ≈ on time
17:36≈ on time ≈ on time
17:43≈ on time ≈ on time
17:47≈ on time ≈ on time
17:57on 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
Thu 19 NovAkkrum 18:13Partial coverage0 min+11 min
Wed 18 NovGrou-Jirnsum 17:59Partial coverage0 min—
Tue 17 NovGrou-Jirnsum 17:59Partial coverage+5 min+5 min
Mon 16 NovGrou-Jirnsum 18:00Partial coverage0 min+2 min
Sun 15 NovKampen Zuid 16:590 min+3 min
Sat 14 NovKampen Zuid 16:580 min—
Fri 13 NovGrou-Jirnsum 18:09Partial coverage+7 min+8 min
Thu 12 NovGrou-Jirnsum 17:59Partial coverage+1 min+1 min
Wed 11 NovGrou-Jirnsum 17:59Partial coverage+2 min+3 min
Tue 10 NovGrou-Jirnsum 17:59Partial coverage+1 min+2 min
Mon 9 NovGrou-Jirnsum 17:59Partial coverage0 min—
Sun 8 NovKampen Zuid 16:580 min—
Sat 7 NovKampen Zuid 16:580 min—
Fri 6 NovGrou-Jirnsum 17:59Partial coverage0 min—
Thu 5 NovGrou-Jirnsum 17:59No data—
Wed 4 NovGrou-Jirnsum 17:59No data—
Tue 3 NovGrou-Jirnsum 17:59Partial coverage0 min—
Mon 2 NovGrou-Jirnsum 17:59No data—
Sun 1 NovKampen Zuid 16:580 min—
Sat 31 OctKampen Zuid 16:580 min—
Fri 30 OctGrou-Jirnsum 18:010 min—
Thu 29 OctGrou-Jirnsum 18:01No data—
Wed 28 OctGrou-Jirnsum 18:01No data—
Tue 27 OctGrou-Jirnsum 18:01No data—
Mon 26 OctGrou-Jirnsum 18:02Partial coverage+2 min+2 min
Sun 25 OctKampen Zuid 16:59No data—
Sat 24 OctKampen Zuid 16:580 min—
Fri 23 OctGrou-Jirnsum 18:02No data—
Thu 22 OctWolvega 17:59No data—
Wed 21 OctGrou-Jirnsum 18:02No data—