Train NS 4256 Den Haag Centraal – Haarlem

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

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: tomorrow 17:55 from Den Haag Centraal · Mon 16 Nov

Next departure 17:55 tomorrow · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 7 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 23 full · 4 partial · 54 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

Worst days

  • Thu 8 Oct Max en route +14 min · last fix heading to Den Haag Mariahoeve +13 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Heemstede-Aerdenhout +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 80% T n=5
  • 100% F n=5
  • 75% 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, 27 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
17:55on time on time
17:58≈ on time ≈ on time
18:01≈ on time ≈ on time
18:06≈ on time ≈ +1 min
18:10≈ on time ≈ +1 min
18:14 / 18:20≈ on time ≈ +1 min
18:25≈ on time ≈ +1 min
18:32≈ on time ≈ +2 min
18:38≈ on time ≈ +2 min
18: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 13 NovHeemstede-Aerdenhout 18:52Partial coverage0 min—
Thu 12 NovLeiden Centraal 18:44+1 min—
Wed 11 NovDe Vink 18:44+2 min+2 min
Tue 10 NovLeiden Centraal 18:440 min—
Mon 9 NovDe Vink 18:440 min—
Sun 8 NovHeemstede-Aerdenhout 18:54+2 min+2 min
Sat 7 NovHeemstede-Aerdenhout 18:520 min—
Fri 6 NovHaarlem 19:040 min—
Thu 5 NovDe Vink 19:040 min—
Wed 4 NovDe Vink 19:07No data—
Tue 3 NovDe Vink 19:05No data—
Mon 2 NovDe Vink 19:040 min—
Sun 1 NovHeemstede-Aerdenhout 18:520 min—
Sat 31 OctHeemstede-Aerdenhout 18:55+3 min+4 min
Fri 30 OctHeemstede-Aerdenhout 18:52Partial coverage0 min—
Thu 29 OctDen Haag Mariahoeve 18:440 min—
Wed 28 OctDe Vink 18:45+2 min+3 min
Tue 27 OctDen Haag Mariahoeve 18:450 min—
Mon 26 OctDe Vink 18:45No data—
Sun 25 OctHeemstede-Aerdenhout 18:52No data—
Sat 24 OctHeemstede-Aerdenhout 18:590 min—
Fri 23 OctHeemstede-Aerdenhout 18:52Partial coverage+2 min+2 min
Thu 22 OctHeemstede-Aerdenhout 18:520 min—
Wed 21 OctHeemstede-Aerdenhout 18:52No data—
Tue 20 OctHeemstede-Aerdenhout 18:50No data—
Mon 19 OctHeemstede-Aerdenhout 18:52No data—
Sun 18 OctHeemstede-Aerdenhout 18:520 min—
Sat 17 OctHeemstede-Aerdenhout 18:520 min—
Fri 16 OctHeemstede-Aerdenhout 18:52No data—
Thu 15 OctVoorhout 18:44No data—