Train NS 4261 Haarlem – Den Haag Centraal

Haarlem 18:17 → Den Haag Centraal 19:04 Daily 0 h 47 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 18:17 from Haarlem · Wed 18 Nov

Next departure 18:17 today · Haarlem
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 13 full · 6 partial · 7 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 21 full · 8 partial · 32 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 Centraal, 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

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

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
18:17on time on time
18:22≈ on time ≈ on time
18:27≈ on time ≈ on time
18:34≈ on time ≈ on time
18:40 / 18:46≈ on time ≈ on time
18:50≈ on time ≈ +1 min
18:53≈ on time ≈ +1 min
18:58≈ on time ≈ +1 min
19:01≈ on time ≈ +1 min
19:04on 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
Tue 17 NovHeemstede-Aerdenhout 19:04Partial coverage0 min—
Mon 16 NovHillegom 19:08Partial coverage+2 min+2 min
Fri 13 NovVoorschoten 19:07+1 min—
Thu 12 NovHeemstede-Aerdenhout 19:09Partial coverage+3 min+3 min
Wed 11 Nov— 19:07+1 min—
Tue 10 NovHeemstede-Aerdenhout 19:04Partial coverage0 min—
Mon 9 Nov— 19:070 min—
Sun 8 NovVoorhout 18:490 min—
Sat 7 NovVoorhout 18:490 min—
Fri 6 NovLeiden Centraal 19:040 min—
Thu 5 NovHaarlem Spaarnwoude 19:04No data—
Wed 4 NovHaarlem Spaarnwoude 19:08No data—
Tue 3 NovHaarlem Spaarnwoude 19:05No data—
Mon 2 NovHalfweg-Zwanenburg 19:040 min—
Sun 1 NovVoorhout 18:490 min—
Sat 31 OctVoorhout 18:500 min—
Fri 30 OctVoorschoten 19:07No data—
Wed 28 Oct— 19:060 min—
Tue 27 Oct— 19:230 min—
Mon 26 Oct— 19:06No data—
Sun 25 OctVoorhout 18:51No data—
Sat 24 OctVoorhout 18:500 min—
Fri 23 OctDen Haag Laan v NOI 19:150 min—
Thu 22 OctVoorhout 19:06Partial coverage0 min—
Wed 21 OctVoorhout 19:06No data—
Tue 20 OctLeiden Centraal 19:10Partial coverage0 min—
Mon 19 OctVoorhout 19:06Partial coverage0 min—
Sun 18 OctVoorhout 18:51+1 min—
Sat 17 OctVoorhout 18:490 min—
Fri 16 OctDen Haag Laan v NOI 19:160 min—