Train NS 4218 Leiden Centraal → Haarlem
NS 4218 Leiden Centraal–Haarlem: final delay under 3 min on 19 of its 19 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:28 (GMT+1).
An alert on this phone or computer when the 4218 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Saturday 21 November 0 min
Next service: tomorrow 08:50 from Leiden Centraal · Mon 23 Nov
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
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 28
- 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=5
- 100% T n=4
- 100% F n=5
- 100% S n=5
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 28 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 08:50 | on time | on time | |
| 08:55 | ≈ on time | ≈ on time | |
| 09:02 | ≈ on time | ≈ +1 min | |
| 09:08 | ≈ on time | ≈ +1 min | |
| 09:13 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Heemstede-Aerdenhout 09:22Partial coverage | 0 min | — |
| Fri 20 Nov | Heemstede-Aerdenhout 09:44 | +1 min | +2 min |
| Thu 19 Nov | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Wed 18 Nov | Heemstede-Aerdenhout 09:23 | 0 min | — |
| Tue 17 Nov | Heemstede-Aerdenhout 09:23 | 0 min | — |
| Mon 16 Nov | Heemstede-Aerdenhout 09:24 | +3 min | +3 min |
| Fri 13 Nov | Heemstede-Aerdenhout 09:23 | +1 min | — |
| Thu 12 Nov | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Wed 11 Nov | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Tue 10 Nov | Heemstede-Aerdenhout 09:24 | +2 min | +2 min |
| Mon 9 Nov | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Sat 7 Nov | Heemstede-Aerdenhout 09:22Partial coverage | 0 min | — |
| Fri 6 Nov | Amsterdam Sloterdijk 09:44 | No data | — |
| Thu 5 Nov | Amsterdam Sloterdijk 09:44 | No data | — |
| Wed 4 Nov | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Tue 3 Nov | Amsterdam Sloterdijk 09:44 | No data | — |
| Mon 2 Nov | Amsterdam Sloterdijk 10:03 | 0 min | — |
| Sat 31 Oct | Heemstede-Aerdenhout 09:22Partial coverage | 0 min | — |
| Fri 30 Oct | Heemstede-Aerdenhout 09:23 | 0 min | — |
| Thu 29 Oct | Heemstede-Aerdenhout 09:24 | No data | — |
| Wed 28 Oct | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Tue 27 Oct | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Mon 26 Oct | Heemstede-Aerdenhout 09:23 | No data | — |
| Sat 24 Oct | Heemstede-Aerdenhout 09:22Partial coverage | 0 min | — |
| Fri 23 Oct | Heemstede-Aerdenhout 09:22 | No data | — |
| Thu 22 Oct | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Wed 21 Oct | Heemstede-Aerdenhout 09:22 | No data | — |
| Tue 20 Oct | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Mon 19 Oct | Heemstede-Aerdenhout 09:22 | 0 min | — |
| Sat 17 Oct | Heemstede-Aerdenhout 09:22Partial coverage | 0 min | — |