Train NS 4212 Leiden Centraal – Haarlem

Leiden Centraal 07:20 → Haarlem 07:43 Mon, Tue, Wed, Thu, Fri, Sat 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heemstede-Aerdenhout at 07:53 +2 min

  1. Leiden Centraal07:20
  2. Voorhout07:25
  3. Hillegom07:32
  4. Heemstede-Aerdenhout07:38
  5. Haarlem07:43

Next service: Monday 07:20 from Leiden Centraal · Mon 9 Nov

Next departure 07:20 Monday · Leiden Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 18 full · 4 partial · 3 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 21 full · 4 partial · 50 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 Haarlem, 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

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

  • Early 0% · 0
  • On time 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
07:20on time on time
07:25≈ on time ≈ on time
07:32≈ on time ≈ on time
07:38≈ on time ≈ +1 min
07:43on 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
Sat 7 NovHeemstede-Aerdenhout 07:53Partial coverage+2 min+2 min
Fri 6 NovAmsterdam Sloterdijk 08:14No data—
Thu 5 NovAmsterdam Sloterdijk 08:14No data—
Wed 4 NovAmsterdam Sloterdijk 08:14+2 min+2 min
Tue 3 NovAmsterdam Sloterdijk 08:140 min—
Mon 2 NovAmsterdam Sloterdijk 08:140 min—
Sat 31 OctHeemstede-Aerdenhout 07:52Partial coverage0 min—
Fri 30 OctHeemstede-Aerdenhout 07:520 min—
Thu 29 OctHeemstede-Aerdenhout 07:520 min—
Wed 28 OctHeemstede-Aerdenhout 07:520 min—
Tue 27 OctHeemstede-Aerdenhout 07:520 min—
Mon 26 OctHeemstede-Aerdenhout 07:530 min—
Sat 24 OctHeemstede-Aerdenhout 07:53Partial coverage+1 min+1 min
Fri 23 OctHeemstede-Aerdenhout 07:53+1 min—
Thu 22 OctHeemstede-Aerdenhout 07:530 min—
Wed 21 OctHeemstede-Aerdenhout 07:520 min—
Tue 20 OctHeemstede-Aerdenhout 07:530 min—
Mon 19 OctHeemstede-Aerdenhout 07:520 min—
Sat 17 OctHeemstede-Aerdenhout 07:52Partial coverage0 min—
Fri 16 OctHeemstede-Aerdenhout 07:520 min—
Thu 15 OctHeemstede-Aerdenhout 07:520 min—
Wed 14 OctHeemstede-Aerdenhout 07:52No data—
Tue 13 OctHeemstede-Aerdenhout 07:520 min—
Mon 12 OctHeemstede-Aerdenhout 07:520 min—
Fri 9 OctHeemstede-Aerdenhout 07:520 min—
Thu 8 OctHeemstede-Aerdenhout 07:53+2 min+2 min
Wed 7 OctHeemstede-Aerdenhout 07:520 min—
Tue 6 OctHeemstede-Aerdenhout 07:520 min—
Mon 5 OctHeemstede-Aerdenhout 07:53No data—
Sat 3 OctHeemstede-Aerdenhout 07:52No data—