Train NS 4393 Den Haag Centraal – Schiphol Airport

Den Haag Centraal 00:12 → Schiphol Airport 00:53 Daily 0 h 41 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:59 0 min

  1. Den Haag Centraal00:12
  2. Den Haag Mariahoeve00:18
  3. Voorschoten00:23
  4. Leiden Centraal00:31
  5. Sassenheim00:37
  6. Hoofddorp00:49
  7. Schiphol Airport00:53

Next service: tomorrow 00:12 from Den Haag Centraal · Wed 11 Nov

Full trip card
Next departure 00:12 tomorrow · Den Haag Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 2 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 27 full · 2 partial · 11 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 Schiphol Airport, 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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=3
  • 100% S n=5
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
Den Haag Centraal
00:12on time on time
Den Haag Laan v NOI
00:15≈ on time ≈ on time
Den Haag Mariahoeve
00:18≈ on time ≈ on time
Voorschoten
00:23≈ on time ≈ on time
De Vink
00:27≈ on time ≈ on time
Leiden Centraal
00:31 / 00:32≈ on time ≈ on time
Sassenheim
00:37≈ on time ≈ on time
Nieuw Vennep
00:44≈ on time ≈ on time
Hoofddorp
00:49≈ on time ≈ on time
Schiphol Airport
00:53on 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
Tue 10 Nov— 00:590 min—
Sun 8 NovHoofddorp 01:040 min—
Sat 7 Nov— 02:040 min—
Fri 6 Nov— 00:54No data—
Thu 5 Nov— 00:540 min—
Wed 4 Nov— 00:540 min—
Tue 3 Nov— 00:540 min—
Sun 1 NovHoofddorp 01:03Partial coverage0 min—
Sat 31 Oct— 02:040 min—
Fri 30 Oct— 00:540 min—
Thu 29 Oct— 01:310 min—
Wed 28 Oct— 00:540 min—
Tue 27 Oct— 00:540 min—
Sun 25 OctHoofddorp 01:040 min—
Sat 24 Oct— 02:050 min—
Fri 23 Oct— 00:590 min—
Thu 22 Oct— 00:540 min—
Wed 21 Oct— 00:550 min—
Tue 20 Oct— 00:550 min—
Sun 18 OctHoofddorp 01:040 min—
Sat 17 OctWeesp 02:040 min—
Fri 16 Oct— 00:55No data—
Thu 15 Oct— 00:540 min—
Wed 14 Oct— 00:540 min—
Tue 13 Oct— 00:570 min—
Sun 11 OctHoofddorp 01:03Partial coverage0 min—
Sat 10 Oct— 02:040 min—
Fri 9 Oct— 00:540 min—
Thu 8 Oct— 00:540 min—
Wed 7 Oct— 00:55+1 min+1 min