Train NS 839 Schiphol Airport – Leeuwarden

Schiphol Airport 11:29 → Leeuwarden 13:44 Daily 2 h 15 min · 9 stops NS (Nederlandse Spoorwegen)

Running now · updated 13:42

Heading to Leeuwarden 0 min

Estimated arrival at Leeuwarden 13:44 · 41 km/h

  1. Schiphol Airport11:29
  2. Amsterdam Zuid11:36
  3. Lelystad Centrum12:16
  4. Zwolle12:44
  5. Meppel13:04
  6. Heerenveen13:27
  7. Leeuwarden13:44

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 22 runs arrived on time.

On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 15 full · 7 partial · 8 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 26 full · 9 partial · 54 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 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

  • Sun 18 Oct Max en route +6 min · last fix heading to Heerenveen +5 min
  • Sat 14 Nov Max en route +9 min · last fix heading to Heerenveen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 33
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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