Train NS 4229 Haarlem – Leiden Centraal

Haarlem 10:17 → Leiden Centraal 10:40 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Voorhout at 10:49 0 min

  1. Haarlem10:17
  2. Heemstede-Aerdenhout10:22
  3. Hillegom10:27
  4. Voorhout10:34
  5. Leiden Centraal10:40

Next service: tomorrow 10:17 from Haarlem · Mon 9 Nov

Next departure 10:17 tomorrow · Haarlem
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 9 full · 7 partial · 12 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 17 full · 7 partial · 59 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: 0 min

Last 30 days

Arrival delay at Leiden 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

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

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

Stops and timetable

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

Last 90 days, 24 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
10:17on time on time
10:22≈ on time ≈ on time
10:27≈ on time ≈ on time
10:34≈ on time ≈ on time
10:40on 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
Sun 8 NovVoorhout 10:49Partial coverage0 min—
Sat 7 NovVoorhout 10:49Partial coverage0 min—
Fri 6 NovDen Haag Laan v NOI 11:19No data—
Thu 5 NovDen Haag Laan v NOI 11:14No data—
Wed 4 NovDen Haag Laan v NOI 11:140 min—
Tue 3 NovDen Haag Laan v NOI 11:18No data—
Mon 2 NovDen Haag Laan v NOI 11:140 min—
Sun 1 NovVoorhout 10:50Partial coverage0 min—
Sat 31 OctVoorhout 10:49Partial coverage0 min—
Fri 30 OctDen Haag Laan v NOI 11:170 min—
Thu 29 OctDen Haag Laan v NOI 11:150 min—
Wed 28 OctDen Haag Laan v NOI 11:160 min—
Tue 27 OctDen Haag Laan v NOI 11:15No data—
Mon 26 OctDen Haag Laan v NOI 11:16No data—
Sun 25 OctVoorhout 10:49No data—
Sat 24 OctVoorhout 10:49Partial coverage0 min—
Fri 23 OctDen Haag Laan v NOI 11:160 min—
Thu 22 OctDen Haag Laan v NOI 11:150 min—
Wed 21 OctDen Haag Laan v NOI 11:17No data—
Tue 20 OctDen Haag Laan v NOI 11:15No data—
Mon 19 OctDen Haag Laan v NOI 11:150 min—
Sun 18 OctVoorhout 10:50Partial coverage+1 min+1 min
Sat 17 OctVoorhout 10:49Partial coverage0 min—
Fri 16 OctDen Haag Laan v NOI 11:170 min—
Thu 15 OctDen Haag Laan v NOI 11:15No data—
Wed 14 OctDen Haag Laan v NOI 11:15No data—
Tue 13 OctDen Haag Laan v NOI 11:16No data—
Mon 12 OctDen Haag Laan v NOI 11:15No data—
Fri 9 OctDen Haag Laan v NOI 11:170 min—
Thu 8 OctDen Haag Laan v NOI 11:160 min—