Train NS 883 Schiphol Airport – Leeuwarden

Schiphol Airport 22:29 → Leeuwarden 00:52 Daily 2 h 23 min · 12 stops NS (Nederlandse Spoorwegen)

Running now · updated 23:40

Heading to Leeuwarden 0 min

Estimated arrival at Leeuwarden 00:52 · 138 km/h

  1. Schiphol Airport22:29
  2. Almere Centrum23:01
  3. Zwolle23:44
  4. Steenwijk00:13
  5. Wolvega00:21
  6. Akkrum00:37
  7. Leeuwarden00:52

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

On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 26 full · 1 partial · 2 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 37 full · 1 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 38 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
22:29on time on time
22:36 / 22:41≈ on time ≈ on time
23:01 / 23:03≈ on time ≈ on time
23:16 / 23:18≈ on time ≈ on time
23:44 / 23:48≈ on time ≈ on time
00:04≈ on time ≈ on time
00:13≈ on time ≈ on time
00:21≈ on time ≈ on time
00:29≈ on time ≈ on time
00:37≈ on time ≈ on time
00:42≈ on time ≈ on time
00:52on time on time

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
Sat 14 NovAmsterdam Zuid 23:39Partial coverage0 min—
Fri 13 Nov— 00:54+1 min+1 min
Thu 12 Nov— 01:040 min—
Wed 11 Nov— 23:440 min—
Tue 10 Nov— 00:530 min—
Mon 9 Nov— 00:530 min—
Sun 8 NovGrou-Jirnsum 00:590 min—
Sat 7 NovLelystad Centrum 00:530 min—
Fri 6 Nov— 22:380 min—
Thu 5 Nov— 01:290 min—
Wed 4 Nov— 00:540 min—
Mon 2 Nov— 00:530 min—
Sun 1 NovGrou-Jirnsum 00:570 min+1 min
Sat 31 OctLelystad Centrum 23:32No data—
Fri 30 Oct— 00:530 min—
Thu 29 Oct— 00:580 min—
Wed 28 Oct— 00:570 min—
Tue 27 Oct— 00:540 min—
Mon 26 Oct— 00:530 min—
Sun 25 OctWolvega 00:37No data—
Sat 24 OctSchiphol Airport 00:310 min—
Fri 23 Oct— 01:080 min—
Thu 22 Oct— 00:530 min—
Wed 21 Oct— 00:530 min—
Tue 20 Oct— 00:530 min—
Mon 19 Oct— 23:460 min—
Sun 18 OctGrou-Jirnsum 01:010 min+3 min
Sat 17 OctGrou-Jirnsum 00:590 min—
Fri 16 Oct— 00:57+2 min+4 min
Thu 15 Oct— 00:530 min—