Train NS 815 Zwolle – Leeuwarden

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

✓ Today’s run finished

Today, last fix heading to Heerenveen at 07:44 0 min

  1. Zwolle06:48
  2. Meppel07:04
  3. Steenwijk07:14
  4. Heerenveen07:27
  5. Leeuwarden07:44

Next service: tomorrow 06:48 from Zwolle · Tue 10 Nov

Next departure 06:48 tomorrow · Zwolle
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 2 full · 18 partial · 2 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 2 full · 22 partial · 39 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: 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 26 Oct Max en route +7 min · last fix heading to Heerenveen +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% 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, 24 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:48on time on time
07:04— —
07:14— —
07:27— —
07:44— —

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 9 NovHeerenveen 07:44Partial coverage0 min—
Fri 6 NovHeerenveen 07:54No data—
Thu 5 NovHeerenveen 07:48No data—
Wed 4 NovHeerenveen 07:49Partial coverage+3 min+4 min
Tue 3 NovHeerenveen 08:13Partial coverage0 min—
Mon 2 NovHeerenveen 07:44Partial coverage0 min—
Fri 30 OctHeerenveen 07:45Partial coverage0 min—
Thu 29 OctHeerenveen 07:42Partial coverage0 min—
Wed 28 OctHeerenveen 07:48Partial coverage0 min—
Tue 27 OctHeerenveen 07:50Partial coverage0 min—
Mon 26 OctHeerenveen 08:00Partial coverage+7 min+7 min
Sat 24 OctWolvega 07:360 min—
Fri 23 OctHeerenveen 07:45Partial coverage0 min—
Thu 22 OctHeerenveen 07:45Partial coverage0 min—
Wed 21 OctHeerenveen 07:46Partial coverage0 min—
Tue 20 OctHeerenveen 07:45Partial coverage0 min—
Mon 19 OctHeerenveen 07:45Partial coverage0 min—
Fri 16 OctHeerenveen 07:45Partial coverage0 min—
Thu 15 OctHeerenveen 07:46Partial coverage0 min—
Wed 14 OctHeerenveen 07:450 min—
Tue 13 OctHeerenveen 07:45Partial coverage0 min—
Mon 12 OctHeerenveen 07:45Partial coverage0 min—
Fri 9 OctHeerenveen 07:41Partial coverage0 min—
Thu 8 OctHeerenveen 07:48Partial coverage+1 min+1 min
Wed 7 OctHeerenveen 07:41Partial coverage+2 min+2 min
Tue 6 OctHeerenveen 07:50Partial coverage+3 min+3 min
Mon 5 OctHeerenveen 07:42No data—
Fri 2 OctHeerenveen 07:42No data—
Thu 1 OctHeerenveen 07:42No data—
Wed 30 SeptHeerenveen 07:43No data—