Train NS 4243 Haarlem – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Den Haag Laan v NOI at 14:44 0 min

  1. Haarlem13:47
  2. Hillegom13:57
  3. Voorhout14:04
  4. De Vink14:20
  5. Voorschoten14:23
  6. Den Haag Laan v NOI14:31
  7. Den Haag Centraal14:34

Next service: tomorrow 13:47 from Haarlem · Wed 18 Nov

Next departure 13:47 tomorrow · Haarlem
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 8 full · 13 partial · 7 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 20 full · 17 partial · 44 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

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

  • Early 3% · 1
  • On time 97% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=8
  • 100% W n=4
  • 100% T n=4
  • 100% F n=7
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 37 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:47on time on time
13:52≈ on time ≈ on time
13:57≈ on time ≈ on time
14:04≈ on time ≈ on time
14:10 / 14:16≈ on time ≈ on time
14:20≈ on time ≈ on time
14:23≈ on time ≈ on time
14:28≈ on time ≈ on time
14:31≈ on time ≈ on time
14: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
Tue 17 NovDen Haag Laan v NOI 14:44Partial coverage0 min—
Mon 16 NovDen Haag Laan v NOI 14:45Partial coverage0 min—
Fri 13 NovDen Haag Laan v NOI 14:44+1 min—
Thu 12 NovDen Haag Laan v NOI 14:44Partial coverage0 min—
Wed 11 NovDen Haag Laan v NOI 14:44Partial coverage0 min—
Tue 10 NovDen Haag Laan v NOI 14:47Partial coverage+1 min+1 min
Mon 9 NovDen Haag Laan v NOI 14:44Partial coverage0 min—
Sun 8 NovVoorhout 14:190 min—
Sat 7 NovVoorhout 14:19+1 min+1 min
Fri 6 NovDen Haag Laan v NOI 14:44No data—
Thu 5 NovDen Haag Laan v NOI 14:44No data—
Wed 4 NovDen Haag Laan v NOI 14:440 min—
Tue 3 NovDen Haag Laan v NOI 14:44No data—
Mon 2 NovDen Haag Laan v NOI 14:44No data—
Sun 1 NovVoorhout 14:210 min—
Sat 31 OctVoorhout 14:190 min—
Fri 30 OctDen Haag Laan v NOI 14:460 min—
Thu 29 OctHaarlem 15:16Partial coverage0 min—
Wed 28 OctDen Haag Laan v NOI 14:45No data—
Tue 27 OctDen Haag Laan v NOI 14:46Partial coverage0 min—
Mon 26 OctDen Haag Laan v NOI 14:46Partial coverage0 min—
Sun 25 OctVoorhout 14:19No data—
Sat 24 OctVoorhout 14:190 min—
Fri 23 OctDen Haag Laan v NOI 14:46No data—
Thu 22 OctDen Haag Laan v NOI 14:45Partial coverage0 min—
Wed 21 OctDen Haag Laan v NOI 14:45Partial coverage0 min—
Tue 20 OctDen Haag Laan v NOI 14:46Partial coverage0 min—
Mon 19 OctDen Haag Laan v NOI 14:45Partial coverage0 min—
Sun 18 OctVoorhout 14:200 min—
Sat 17 OctVoorhout 14:20No data—