Train NS 4235 Haarlem – Den Haag Centraal

Haarlem 11:47 → Den Haag Centraal 12:35 Daily 0 h 48 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Den Haag Laan v NOI at 12:47 0 min

  1. Haarlem11:47
  2. Hillegom11:57
  3. Voorhout12:04
  4. De Vink12:21
  5. Voorschoten12:24
  6. Den Haag Laan v NOI12:32
  7. Den Haag Centraal12:35

Next service: tomorrow 11:47 from Haarlem · Sat 21 Nov

Next departure 11:47 tomorrow · Haarlem
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 7 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 33 full · 1 partial · 48 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

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

  • Early 0% · 0
  • On time 100% · 34
  • 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=7
  • 100% W n=5
  • 100% T n=5
  • 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, 34 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
11:47on time on time
11:52≈ on time ≈ on time
11:57≈ on time ≈ on time
12:04≈ on time ≈ on time
12:09 / 12:17≈ on time ≈ on time
12:21≈ on time ≈ on time
12:24≈ on time ≈ on time
12:29≈ on time ≈ on time
12:32≈ on time ≈ +1 min
12:35on 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
Fri 20 NovDen Haag Laan v NOI 12:47Partial coverage0 min—
Thu 19 NovDen Haag Laan v NOI 12:47+1 min+2 min
Wed 18 NovDen Haag Laan v NOI 12:440 min—
Tue 17 NovDen Haag Laan v NOI 12:440 min—
Mon 16 NovDen Haag Laan v NOI 12:450 min—
Fri 13 NovDen Haag Laan v NOI 12:470 min—
Thu 12 NovDen Haag Laan v NOI 12:44+1 min—
Wed 11 NovDen Haag Laan v NOI 12:440 min—
Tue 10 NovDen Haag Laan v NOI 12:440 min—
Mon 9 NovDen Haag Laan v NOI 12:48+2 min+3 min
Sun 8 NovVoorhout 12:19+1 min—
Sat 7 NovVoorhout 12:190 min—
Fri 6 NovDen Haag Laan v NOI 12:47No data—
Thu 5 NovDen Haag Laan v NOI 12:44No data—
Wed 4 NovDen Haag Laan v NOI 12:440 min—
Tue 3 NovDen Haag Laan v NOI 12:440 min—
Mon 2 NovDen Haag Laan v NOI 12:44No data—
Sun 1 NovVoorhout 12:200 min—
Sat 31 OctVoorhout 12:19No data—
Fri 30 OctDen Haag Laan v NOI 12:470 min—
Thu 29 OctDen Haag Laan v NOI 12:450 min—
Wed 28 OctDen Haag Laan v NOI 12:45No data—
Tue 27 OctDen Haag Laan v NOI 12:460 min—
Mon 26 OctDen Haag Laan v NOI 12:450 min—
Sun 25 OctVoorhout 12:20No data—
Sat 24 OctVoorhout 12:190 min—
Fri 23 OctDen Haag Laan v NOI 12:46No data—
Thu 22 OctDen Haag Laan v NOI 12:450 min—
Wed 21 OctDen Haag Laan v NOI 12:460 min—
Tue 20 OctDen Haag Laan v NOI 12:450 min—