Train NS 820 Leeuwarden – Schiphol Airport

Leeuwarden 06:16 → Schiphol Airport 08:30 Daily 2 h 14 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Zuid at 08:38 0 min

  1. Leeuwarden06:16
  2. Heerenveen06:32
  3. Meppel06:56
  4. Zwolle07:11
  5. Lelystad Centrum07:41
  6. Amsterdam Zuid08:18
  7. Schiphol Airport08:30

Next service: tomorrow 06:16 from Leeuwarden · Thu 22 Oct

Full trip card
Next departure 06:16 tomorrow · Leeuwarden
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 6 full · 10 partial · 14 no data
On-time · 90 days
75%
12/16 runs under 3 min
RT coverage: 6 full · 10 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Schiphol Airport, 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 +29 min · last fix heading to Amsterdam Zuid +29 min
  • Fri 9 Oct Max en route +16 min · last fix heading to Amsterdam Zuid +16 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Amsterdam Zuid +3 min
  • Sat 17 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 12
  • 3–10 min 13% · 2
  • 10–30 min 13% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 67% W n=3
  • 50% T n=2
  • 50% F n=2
  • 50% S n=2
  • 100% S n=2

Stops and timetable

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

StopSched.
Leeuwarden
06:16
Heerenveen
06:32
Steenwijk
06:46
Meppel
06:56
Zwolle
07:11 / 07:16
Lelystad Centrum
07:41 / 07:42
Almere Centrum
07:56 / 07:58
Amsterdam Zuid
08:18 / 08:24
Schiphol Airport
08:30

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.

Recent runs

DateLast stopFinalMax
Wed 21 OctAmsterdam Zuid 08:380 min—
Tue 20 OctAmsterdam Zuid 08:38Partial coverage0 min—
Mon 19 OctAmsterdam Zuid 08:38Partial coverage0 min—
Sun 18 OctAmsterdam Zuid 08:38+2 min+2 min
Sat 17 OctAmsterdam Zuid 08:41+3 min+4 min
Fri 16 OctAmsterdam Zuid 08:38Partial coverage0 min—
Thu 15 OctAmsterdam Zuid 08:38Partial coverage0 min—
Wed 14 OctAmsterdam Zuid 08:38Partial coverage0 min—
Tue 13 OctAmsterdam Zuid 08:380 min—
Mon 12 OctAmsterdam Zuid 08:38Partial coverage0 min—
Sun 11 OctAmsterdam Zuid 08:38+1 min—
Sat 10 OctAmsterdam Zuid 08:380 min—
Fri 9 OctAmsterdam Zuid 09:00Partial coverage+16 min+16 min
Thu 8 OctAmsterdam Zuid 08:39Partial coverage+3 min+3 min
Wed 7 OctAmsterdam Zuid 08:52Partial coverage+29 min+29 min
Tue 6 OctAmsterdam Zuid 08:38Partial coverage+1 min—
Mon 5 OctAmsterdam Zuid 08:39No data—
Sun 4 OctAmsterdam Zuid 08:38No data—
Sat 3 OctAmsterdam Zuid 08:39No data—
Fri 2 OctAmsterdam Zuid 08:38No data—
Thu 1 OctAmsterdam Zuid 08:38No data—
Wed 30 SeptAmsterdam Zuid 08:38No data—
Tue 29 SeptAmsterdam Zuid 08:38No data—
Mon 28 SeptAmsterdam Zuid 08:38No data—
Sun 27 SeptAmsterdam Zuid 08:39No data—
Sat 26 SeptAmsterdam Zuid 08:41No data—
Fri 25 SeptAmsterdam Zuid 08:38No data—
Thu 24 SeptAmsterdam Zuid 08:41No data—
Wed 23 SeptAmsterdam Zuid 08:39No data—
Tue 22 SeptAmsterdam Zuid 08:41No data—