Train NS 613 Zwolle – Leeuwarden

Zwolle 06:18 → Leeuwarden 07:14 Mon, Tue, Wed, Thu, Fri 0 h 56 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 06:18 from Zwolle · Thu 5 Nov

Next departure 06:18 today · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 1 full · 20 partial · 1 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 1 full · 21 partial · 40 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: +1 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 7 Oct Max en route +19 min · last fix heading to Grou-Jirnsum +19 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 95% · 21
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
06:18on time on time
06:34— —
06:44— —
06:57— —
07:14— —

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
Wed 4 NovHeerenveen 07:14Partial coverage+1 min—
Tue 3 NovHeerenveen 07:09No data—
Mon 2 NovHeerenveen 07:14Partial coverage0 min—
Fri 30 OctHeerenveen 07:12Partial coverage0 min—
Thu 29 OctHeerenveen 07:12Partial coverage0 min—
Wed 28 OctHeerenveen 07:16Partial coverage0 min—
Tue 27 OctHeerenveen 07:16Partial coverage0 min—
Mon 26 OctHeerenveen 07:15Partial coverage0 min—
Sat 24 OctWolvega 07:070 min+1 min
Fri 23 OctHeerenveen 07:15Partial coverage0 min—
Thu 22 OctHeerenveen 07:15Partial coverage0 min—
Wed 21 OctHeerenveen 07:15Partial coverage0 min—
Tue 20 OctHeerenveen 07:11Partial coverage0 min—
Mon 19 OctHeerenveen 07:13Partial coverage0 min+1 min
Fri 16 OctHeerenveen 07:16Partial coverage+1 min+1 min
Thu 15 OctHeerenveen 07:15Partial coverage0 min—
Wed 14 OctHeerenveen 07:16Partial coverage+1 min—
Tue 13 OctHeerenveen 07:15Partial coverage0 min—
Mon 12 OctHeerenveen 07:15Partial coverage0 min—
Fri 9 OctHeerenveen 07:15Partial coverage0 min—
Thu 8 OctHeerenveen 07:16Partial coverage+2 min+2 min
Wed 7 OctGrou-Jirnsum 07:43Partial coverage+19 min+19 min
Tue 6 OctHeerenveen 07:15Partial coverage0 min—
Mon 5 OctHeerenveen 07:12No data—
Fri 2 OctHeerenveen 07:12No data—
Thu 1 OctHeerenveen 07:12No data—
Wed 30 SeptHeerenveen 07:11No data—
Tue 29 SeptHeerenveen 07:11No data—
Mon 28 SeptHeerenveen 07:12No data—
Fri 25 SeptHeerenveen 07:12No data—