Train NS 852 Leeuwarden – Schiphol Airport

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

Running now · updated 16:26

Heading to Schiphol Airport No data

Estimated arrival at Schiphol Airport 16:30 · 109 km/h

  1. Leeuwarden14:16
  2. Heerenveen14:32
  3. Meppel14:56
  4. Zwolle15:11
  5. Lelystad Centrum15:41
  6. Amsterdam Zuid16:18
  7. Schiphol Airport16:30
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 14 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 4 full · 14 partial · 71 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: +2 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

  • Mon 5 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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 10Today
14:16on time on time
14:32— —
14:46— —
14:56— —
15:11 / 15:16— —
15:41 / 15:42— —
15:56 / 15:58— —
16:18 / 16:24— —
16: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
Thu 5 NovAmsterdam Zuid 16:25No data—
Wed 4 NovAmsterdam Zuid 16:38Partial coverage0 min—
Tue 3 NovAmsterdam Zuid 16:38No data—
Mon 2 NovAmsterdam Zuid 16:38No data—
Sun 1 NovAmsterdam Zuid 16:38Partial coverage0 min+8 min
Sat 31 OctAmsterdam Zuid 16:38Partial coverage0 min—
Fri 30 OctAmsterdam Zuid 16:38No data—
Thu 29 OctAmsterdam Zuid 16:38No data—
Wed 28 OctAmsterdam Zuid 16:38Partial coverage0 min—
Tue 27 OctAmsterdam Zuid 16:380 min—
Mon 26 OctAmsterdam Zuid 16:38No data—
Sun 25 OctAmsterdam Zuid 16:41No data—
Sat 24 OctAmsterdam Zuid 16:380 min—
Fri 23 OctAmsterdam Zuid 16:38No data—
Thu 22 OctAmsterdam Zuid 16:38Partial coverage0 min—
Wed 21 OctAmsterdam Zuid 16:53No data—
Tue 20 OctAmsterdam Zuid 16:38Partial coverage0 min—
Mon 19 OctAmsterdam Zuid 16:40No data—
Sun 18 OctAmsterdam Zuid 16:38+2 min+2 min
Sat 17 OctAmsterdam Zuid 16:38No data—
Fri 16 OctAmsterdam Zuid 16:38Partial coverage0 min—
Thu 15 OctAmsterdam Zuid 16:38No data—
Wed 14 OctAmsterdam Zuid 16:38No data—
Tue 13 OctAmsterdam Zuid 16:38No data—
Mon 12 OctAmsterdam Zuid 16:38Partial coverage0 min—
Sun 11 OctAmsterdam Zuid 16:40Partial coverage+2 min+2 min
Sat 10 OctAmsterdam Zuid 16:38Partial coverage0 min—
Fri 9 OctAmsterdam Zuid 16:38Partial coverage+4 min+4 min
Thu 8 OctAmsterdam Zuid 16:38Partial coverage+1 min+1 min
Wed 7 OctAmsterdam Zuid 16:38Partial coverage0 min—