Train NS 4240 Den Haag Centraal – Haarlem

Den Haag Centraal 13:55 → Haarlem 14:43 Daily 0 h 48 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heemstede-Aerdenhout at 14:52 0 min

  1. Den Haag Centraal13:55
  2. Den Haag Mariahoeve14:01
  3. Voorschoten14:06
  4. Leiden Centraal14:14
  5. Voorhout14:25
  6. Heemstede-Aerdenhout14:38
  7. Haarlem14:43

Next service: tomorrow 13:55 from Den Haag Centraal · Sat 21 Nov

Next departure 13:55 tomorrow · Den Haag Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 20 full · 3 partial · 5 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 27 full · 4 partial · 51 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 Haarlem, 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

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

  • Early 0% · 0
  • On time 100% · 31
  • 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=4
  • 100% W n=5
  • 100% T n=6
  • 100% F n=5
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 31 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
13:55on time on time
13:58≈ on time ≈ on time
14:01≈ on time ≈ on time
14:06≈ on time ≈ on time
14:10≈ on time ≈ +1 min
14:14 / 14:20≈ on time ≈ +1 min
14:25≈ on time ≈ +1 min
14:32≈ on time ≈ +1 min
14:38≈ on time ≈ +2 min
14:43on 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 NovHeemstede-Aerdenhout 14:52Partial coverage0 min—
Thu 19 NovHeemstede-Aerdenhout 14:520 min—
Wed 18 NovHeemstede-Aerdenhout 14:520 min—
Tue 17 NovHeemstede-Aerdenhout 14:520 min—
Mon 16 NovHeemstede-Aerdenhout 14:55+2 min+2 min
Fri 13 NovHeemstede-Aerdenhout 14:52Partial coverage0 min—
Thu 12 NovHeemstede-Aerdenhout 14:54+2 min+2 min
Wed 11 NovHeemstede-Aerdenhout 14:520 min—
Tue 10 NovHeemstede-Aerdenhout 14:54+2 min+3 min
Mon 9 NovHeemstede-Aerdenhout 14:520 min—
Sun 8 NovHeemstede-Aerdenhout 14:530 min—
Sat 7 NovHeemstede-Aerdenhout 14:520 min—
Fri 6 NovAmsterdam Sloterdijk 15:23No data—
Thu 5 NovAmsterdam Sloterdijk 15:140 min—
Wed 4 NovAmsterdam Sloterdijk 15:140 min—
Tue 3 NovAmsterdam Sloterdijk 15:15No data—
Mon 2 NovAmsterdam Sloterdijk 15:14No data—
Sun 1 NovHeemstede-Aerdenhout 14:530 min—
Sat 31 OctHeemstede-Aerdenhout 14:55+3 min+3 min
Fri 30 OctHeemstede-Aerdenhout 14:52Partial coverage0 min—
Thu 29 OctHeemstede-Aerdenhout 14:530 min—
Wed 28 OctHeemstede-Aerdenhout 14:520 min—
Tue 27 OctHeemstede-Aerdenhout 14:520 min—
Mon 26 OctHeemstede-Aerdenhout 14:52No data—
Sun 25 OctHeemstede-Aerdenhout 14:52No data—
Sat 24 OctHeemstede-Aerdenhout 14:520 min—
Fri 23 OctHeemstede-Aerdenhout 14:540 min—
Thu 22 OctHeemstede-Aerdenhout 14:560 min—
Wed 21 OctHeemstede-Aerdenhout 14:53No data—
Tue 20 OctHeemstede-Aerdenhout 14:53No data—