Train NS 4263 Haarlem – Den Haag Centraal

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

It has not run yet today

Last recorded run: Monday 16 November +2 min

Next service: today 18:47 from Haarlem · Tue 17 Nov

Next departure 18:47 today · Haarlem
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 7 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 31 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: +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

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

  • Early 0% · 0
  • On time 100% · 27
  • 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=3
  • 100% W n=2
  • 100% T n=4
  • 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, 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
18:47on time on time
18:52≈ on time ≈ on time
18:57≈ on time ≈ on time
19:04≈ on time ≈ on time
19:10 / 19:16≈ on time ≈ +1 min
19:20≈ on time ≈ +1 min
19:23≈ on time ≈ +1 min
19:28≈ on time ≈ +1 min
19:31≈ on time ≈ +1 min
19:34on 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
Mon 16 Nov— 19:38+2 min+2 min
Fri 13 NovHillegom 19:340 min—
Thu 12 Nov— 19:340 min—
Wed 11 Nov— 19:340 min—
Tue 10 Nov— 19:340 min—
Mon 9 Nov— 19:340 min—
Sun 8 NovVoorhout 19:190 min—
Sat 7 NovVoorhout 19:190 min—
Fri 6 NovHaarlem 19:37+2 min+2 min
Thu 5 Nov— 19:34No data—
Wed 4 Nov— 19:34No data—
Tue 3 Nov— 19:34No data—
Mon 2 NovHaarlem 19:340 min—
Sun 1 NovVoorhout 19:190 min—
Sat 31 OctVoorhout 19:190 min—
Fri 30 OctHeemstede-Aerdenhout 19:060 min—
Thu 29 Oct— 19:350 min—
Wed 28 Oct— 19:350 min—
Tue 27 Oct— 20:260 min—
Mon 26 Oct— 19:37No data—
Sun 25 OctVoorhout 19:22No data—
Sat 24 OctVoorhout 19:220 min—
Fri 23 OctDen Haag Mariahoeve 19:42+1 min—
Thu 22 Oct— 19:360 min—
Wed 21 Oct— 19:36No data—
Tue 20 Oct— 19:35No data—
Mon 19 Oct— 19:350 min—
Sun 18 OctVoorhout 19:190 min—
Sat 17 OctVoorhout 19:190 min—
Fri 16 OctDen Haag Laan v NOI 19:46No data—