Train NS 851 Schiphol Airport – Leeuwarden

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 14:30 from Schiphol Airport · Wed 18 Nov

Next departure 14:30 today · Schiphol Airport
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 9 full · 9 partial · 11 no data
On-time · 90 days
83%
24/29 runs under 3 min
RT coverage: 15 full · 14 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Fri 9 Oct Max en route +13 min · last fix heading to Heerenveen +12 min
  • Sun 15 Nov Max en route +13 min · last fix heading to Heerenveen +12 min
  • Sat 10 Oct Max en route +12 min · last fix heading to Heerenveen +11 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Heerenveen +4 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Heerenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 24
  • 3–10 min 7% · 2
  • 10–30 min 10% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=3
  • 100% T n=3
  • 50% F n=2
  • 60% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 29 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
14:30on time on time
14:37 / 14:41≈ on time ≈ +1 min
15:01 / 15:03≈ on time ≈ +3 min
15:16 / 15:18≈ on time ≈ +4 min
15:44 / 15:48≈ on time ≈ +6 min
16:04≈ on time ≈ +8 min
16:14≈ on time ≈ +9 min
16:27≈ on time ≈ +10 min
16:44on time +12 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
Tue 17 NovHeerenveen 16:44Partial coverage0 min—
Mon 16 NovHeerenveen 16:45Partial coverage0 min—
Sun 15 NovHeerenveen 17:09+12 min+13 min
Sat 14 NovHeerenveen 16:440 min—
Fri 13 NovHeerenveen 16:440 min—
Thu 12 NovHeerenveen 16:44Partial coverage0 min—
Wed 11 NovHeerenveen 16:44Partial coverage0 min—
Tue 10 NovHeerenveen 16:44Partial coverage0 min—
Mon 9 NovHeerenveen 16:44Partial coverage0 min—
Sun 8 NovHeerenveen 16:450 min—
Sat 7 NovHeerenveen 16:440 min—
Fri 6 NovHeerenveen 16:47No data—
Thu 5 NovHeerenveen 16:44No data—
Wed 4 NovHeerenveen 16:48Partial coverage+3 min+3 min
Tue 3 NovHeerenveen 16:44No data—
Mon 2 NovHeerenveen 16:44No data—
Sun 1 NovHeerenveen 16:50+2 min+3 min
Sat 31 OctHeerenveen 16:50+3 min+4 min
Fri 30 OctHeerenveen 16:51No data—
Thu 29 OctHeerenveen 16:48No data—
Wed 28 OctHeerenveen 16:45No data—
Tue 27 OctHeerenveen 16:450 min—
Mon 26 OctHeerenveen 16:45No data—
Sun 25 OctWolvega 16:37No data—
Sat 24 OctWolvega 16:370 min+1 min
Fri 23 OctHeerenveen 16:43No data—
Thu 22 OctHeerenveen 16:45Partial coverage0 min—
Wed 21 OctHeerenveen 16:45No data—
Tue 20 OctHeerenveen 16:46Partial coverage0 min—
Mon 19 OctHeerenveen 16:460 min—