Train NS 4287 Haarlem – Den Haag HS

Haarlem 00:57 → Den Haag HS 01:39 Daily 0 h 42 min · 10 stops NS (Nederlandse Spoorwegen)

Running now · updated 01:50

Heading to Den Haag HS 0 min

Estimated arrival at Den Haag HS 01:39 · 1 km/h

  1. Haarlem00:57
  2. Hillegom01:07
  3. Voorhout01:14
  4. De Vink01:24
  5. Voorschoten01:27
  6. Den Haag Laan v NOI01:36
  7. Den Haag HS01:39

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

On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 3 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Den Haag HS, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
00:57on time on time
01:02≈ on time ≈ on time
01:07≈ on time ≈ on time
01:14≈ on time ≈ on time
01:19 / 01:20≈ on time ≈ on time
01:24≈ on time ≈ on time
01:27≈ on time ≈ +1 min
01:33≈ on time ≈ +1 min
01:36≈ on time ≈ +1 min
01:39on time +1 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
Sat 7 Nov— 01:490 min—
Fri 6 Nov— 01:480 min—
Thu 5 Nov— 01:440 min—
Tue 3 Nov— 01:470 min—
Mon 2 NovDen Haag Laan v NOI 01:53+1 min+1 min
Sun 1 Nov— 01:42No data—
Sat 31 Oct— 01:420 min—
Fri 30 Oct— 01:470 min—
Thu 29 Oct— 01:460 min—
Wed 28 Oct— 01:510 min—
Tue 27 Oct— 01:450 min—
Mon 26 OctDen Haag Laan v NOI 01:590 min—
Sun 25 Oct— 01:40No data—
Sat 24 Oct— 01:41+1 min—
Fri 23 Oct— 01:470 min—
Thu 22 Oct— 01:500 min—
Wed 21 Oct— 01:440 min—
Tue 20 Oct— 01:440 min—
Mon 19 OctDen Haag Laan v NOI 01:490 min—
Sun 18 OctDen Haag Mariahoeve 01:47No data—
Sat 17 Oct— 01:44+1 min+4 min
Fri 16 Oct— 01:500 min—
Thu 15 Oct— 02:180 min—
Wed 14 Oct— 01:490 min—
Tue 13 Oct— 01:460 min—
Sun 11 Oct— 01:410 min—
Sat 10 Oct— 01:43+2 min+2 min
Fri 9 Oct— 01:470 min—
Thu 8 Oct— 01:460 min—
Wed 7 Oct— 01:440 min—