Train NS 844 Leeuwarden – Schiphol Airport

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 12:16 from Leeuwarden · Thu 5 Nov

Next departure 12:16 today · Leeuwarden
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 2 full · 13 partial · 14 no data
On-time · 90 days
82%
14/17 runs under 3 min
RT coverage: 2 full · 15 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 9 Oct Max en route +12 min · last fix heading to Amsterdam Zuid +12 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Amsterdam Zuid +5 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Amsterdam Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 14
  • 3–10 min 12% · 2
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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