Train NS 9013 Zwolle – Leeuwarden

Zwolle 05:57 → Leeuwarden 06:57 Mon, Tue, Wed, Thu, Fri 1 h 00 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 05:57 from Zwolle · Mon 9 Nov

Next departure 05:57 Monday · Zwolle
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 2 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 0 full · 22 partial · 41 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

  • Wed 14 Oct Max en route +5 min · last fix heading to Grou-Jirnsum +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Grou-Jirnsum +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 80% W n=5
  • 80% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
05:57on time on time
06:12— —
06:21— —
06:29— —
06:36— —
06:43— —
06:47— —
06:57— —

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
Fri 6 NovGrou-Jirnsum 07:02No data—
Thu 5 NovGrou-Jirnsum 07:04Partial coverage0 min—
Wed 4 NovGrou-Jirnsum 07:02Partial coverage0 min—
Tue 3 NovGrou-Jirnsum 07:03Partial coverage+1 min+2 min
Mon 2 NovGrou-Jirnsum 07:02No data—
Fri 30 OctGrou-Jirnsum 07:03Partial coverage+1 min+1 min
Thu 29 OctGrou-Jirnsum 07:05Partial coverage+3 min+3 min
Wed 28 OctGrou-Jirnsum 07:05Partial coverage+2 min+3 min
Tue 27 OctGrou-Jirnsum 07:02Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 07:04Partial coverage+2 min+3 min
Fri 23 OctGrou-Jirnsum 07:03Partial coverage0 min+2 min
Thu 22 OctGrou-Jirnsum 07:03Partial coverage+1 min+2 min
Wed 21 OctGrou-Jirnsum 07:03Partial coverage+1 min+1 min
Tue 20 OctGrou-Jirnsum 07:03Partial coverage+1 min+2 min
Mon 19 OctGrou-Jirnsum 07:02Partial coverage0 min—
Fri 16 OctGrou-Jirnsum 07:01Partial coverage0 min—
Thu 15 OctGrou-Jirnsum 07:01Partial coverage0 min—
Wed 14 OctGrou-Jirnsum 07:06Partial coverage+4 min+5 min
Tue 13 OctGrou-Jirnsum 07:02Partial coverage0 min—
Mon 12 OctGrou-Jirnsum 07:02Partial coverage0 min—
Fri 9 OctGrou-Jirnsum 07:02Partial coverage0 min+1 min
Thu 8 OctGrou-Jirnsum 07:02Partial coverage+1 min—
Wed 7 OctGrou-Jirnsum 07:01Partial coverage0 min—
Tue 6 OctGrou-Jirnsum 07:01Partial coverage0 min—
Mon 5 OctGrou-Jirnsum 07:03No data—
Fri 2 OctGrou-Jirnsum 07:03No data—
Thu 1 OctGrou-Jirnsum 07:02No data—
Wed 30 SeptGrou-Jirnsum 07:02No data—
Tue 29 SeptGrou-Jirnsum 07:02No data—
Mon 28 SeptGrou-Jirnsum 07:02No data—