Train NS 823 Schiphol Airport – Leeuwarden

Schiphol Airport 07:30 → Leeuwarden 09:44 Daily 2 h 14 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heerenveen at 09:43 0 min

  1. Schiphol Airport07:30
  2. Amsterdam Zuid07:37
  3. Lelystad Centrum08:16
  4. Zwolle08:44
  5. Meppel09:04
  6. Heerenveen09:27
  7. Leeuwarden09:44

Next service: tomorrow 07:30 from Schiphol Airport · Tue 17 Nov

Next departure 07:30 tomorrow · Schiphol Airport
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 13 full · 10 partial · 7 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 17 full · 13 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 31 Oct Max en route +4 min · last fix heading to Heerenveen +4 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Heerenveen +3 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 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • 83% S n=6
  • 80% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
07:30on time on time
07:37 / 07:41≈ on time ≈ on time
08:01 / 08:03≈ on time ≈ +1 min
08:16 / 08:18≈ on time ≈ +1 min
08:44 / 08:48≈ on time ≈ +2 min
09:04≈ on time ≈ +2 min
09:14≈ on time ≈ +2 min
09:27≈ on time ≈ +2 min
09:44on time +3 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 NovHeerenveen 09:43Partial coverage0 min—
Sun 15 NovHeerenveen 09:52+3 min+4 min
Sat 14 NovHeerenveen 09:48+2 min+2 min
Fri 13 NovHeerenveen 09:440 min—
Thu 12 NovHeerenveen 09:44Partial coverage0 min—
Wed 11 NovHeerenveen 09:44Partial coverage0 min—
Tue 10 NovHeerenveen 09:44Partial coverage0 min—
Mon 9 NovHeerenveen 09:44Partial coverage0 min—
Sun 8 NovHeerenveen 09:440 min—
Sat 7 NovHeerenveen 09:49+2 min+2 min
Fri 6 NovHeerenveen 09:44No data—
Thu 5 NovHeerenveen 09:44No data—
Wed 4 NovHeerenveen 09:44Partial coverage0 min—
Tue 3 NovHeerenveen 09:44Partial coverage0 min—
Mon 2 NovAmsterdam Zuid 09:520 min—
Sun 1 NovHeerenveen 09:450 min—
Sat 31 OctHeerenveen 09:41+4 min+4 min
Fri 30 OctHeerenveen 09:550 min—
Thu 29 OctHeerenveen 09:48Partial coverage0 min—
Wed 28 OctHeerenveen 09:46Partial coverage0 min—
Tue 27 OctHeerenveen 09:46No data—
Mon 26 OctHeerenveen 09:45Partial coverage0 min—
Sun 25 OctWolvega 09:36No data—
Sat 24 OctWolvega 09:37+3 min+3 min
Fri 23 OctHeerenveen 09:460 min—
Thu 22 OctHeerenveen 10:01No data—
Wed 21 OctHeerenveen 09:43No data—
Tue 20 OctHeerenveen 09:450 min—
Mon 19 OctHeerenveen 09:45No data—
Sun 18 OctHeerenveen 09:450 min—