Train NS 4282 Leiden Centraal – Haarlem
✓ Today’s run finished
Today, last fix heading to — at 01:34 0 min
- Leiden Centraal00:50
- Voorhout00:55
- Hillegom01:02
- Heemstede-Aerdenhout01:08
- Haarlem01:13
Next service: Friday 00:50 from Leiden Centraal · Fri 13 Nov
Next departure 00:50 Friday · Leiden Centraal
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 2 no data
On-time · 90 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 3 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
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
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 4
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=3
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 00:50 | |
| 00:55 | |
| 01:02 | |
| 01:08 | |
| 01:13 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | — 01:34 | 0 min | — |
| Sun 1 Nov | — 01:23 | No data | — |
| Sun 25 Oct | — 01:17 | 0 min | — |
| Sat 24 Oct | — 01:15 | 0 min | — |
| Sun 18 Oct | Heemstede-Aerdenhout 01:22 | No data | — |
| Sat 17 Oct | — 01:15 | +1 min | +1 min |
| Mon 28 Sept | De Vink 00:51 | No data | — |