Train NS 860 Leeuwarden – Schiphol Airport

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 16:16 from Leeuwarden · Tue 17 Nov

Next departure 16:16 today · Leeuwarden
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 2 full · 15 partial · 12 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 4 full · 22 partial · 62 no data
Typical delay
+1min
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 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

  • Thu 12 Nov Max en route +4 min · last fix heading to Almere Centrum +4 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Almere Centrum +4 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Almere Centrum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 22
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 67% W n=3
  • 50% T n=2
  • 100% F n=4
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 26 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
16:16on time on time
16:32— —
16:46— —
16:56— —
17:11 / 17:16— —
17:41 / 17:42— —
17:56 / 17:58— —
18:18 / 18:24— —
18: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.

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 NovAmsterdam Zuid 18:38Partial coverage0 min—
Sun 15 NovAmsterdam Zuid 18:39Partial coverage+2 min+2 min
Sat 14 NovAmsterdam Zuid 18:38Partial coverage0 min—
Fri 13 NovAmsterdam Zuid 18:38Partial coverage+2 min+2 min
Thu 12 NovAlmere Centrum 18:39Partial coverage+4 min+4 min
Wed 11 NovAlmere Centrum 18:29Partial coverage0 min—
Tue 10 NovAlmere Centrum 18:34Partial coverage+1 min+2 min
Mon 9 NovAlmere Centrum 18:34Partial coverage+3 min+3 min
Sun 8 NovAmsterdam Zuid 18:39Partial coverage+3 min+3 min
Sat 7 NovLelystad Centrum 17:57Partial coverage0 min—
Fri 6 NovAmsterdam Zuid 18:38Partial coverage+2 min+2 min
Thu 5 NovAlmere Centrum 18:29No data—
Wed 4 NovAlmere Centrum 18:29No data—
Tue 3 NovAlmere Centrum 18:290 min—
Mon 2 NovAlmere Centrum 18:12No data—
Sun 1 NovAmsterdam Zuid 18:38Partial coverage0 min—
Sat 31 OctAmsterdam Zuid 18:40Partial coverage+4 min+4 min
Fri 30 OctAmsterdam Zuid 18:38Partial coverage0 min—
Thu 29 OctAlmere Centrum 18:32No data—
Wed 28 OctAlmere Centrum 18:31Partial coverage0 min—
Tue 27 OctAlmere Centrum 18:32No data—
Mon 26 OctAlmere Centrum 18:31No data—
Sun 25 OctAmsterdam Zuid 18:38No data—
Sat 24 OctAmsterdam Zuid 18:380 min—
Fri 23 OctAmsterdam Zuid 18:38No data—
Thu 22 OctAmsterdam Zuid 18:38No data—
Wed 21 OctAmsterdam Zuid 18:34No data—
Tue 20 OctAmsterdam Zuid 18:38No data—
Mon 19 OctAmsterdam Zuid 18:38No data—
Sun 18 OctAmsterdam Zuid 18:38+1 min+1 min