Train NS 4279 Haarlem → Leiden Centraal
NS 4279 Haarlem–Leiden Centraal: final delay under 3 min on 17 of its 17 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 08:50 (GMT+1).
An alert on this phone or computer when the 4279 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November 0 min
Next service: today 22:47 from Haarlem · Sun 22 Nov
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
Worst days
- Wed 7 Oct Max en route +10 min · last fix heading to — +10 min
- Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
- Fri 9 Oct Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 24
- 3–10 min 7% · 2
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=3
- 80% W n=5
- 100% T n=4
- 83% F n=6
- 100% S n=2
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 22:47 | on time | on time | |
| 22:52 | ≈ on time | ≈ +1 min | |
| 22:57 | ≈ on time | ≈ +2 min | |
| 23:04 | ≈ on time | ≈ +2 min | |
| 23:10 | on time | +3 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 | — 23:09 | 0 min | — |
| Fri 20 Nov | — 23:14 | +1 min | +1 min |
| Thu 19 Nov | — 23:09 | 0 min | — |
| Wed 18 Nov | — 23:09 | 0 min | — |
| Tue 17 Nov | — 23:09 | 0 min | — |
| Fri 13 Nov | — 23:09 | 0 min | — |
| Thu 12 Nov | — 23:09 | 0 min | — |
| Wed 11 Nov | — 23:09 | 0 min | — |
| Tue 10 Nov | — 23:09 | 0 min | — |
| Mon 9 Nov | — 23:14 | +1 min | +1 min |
| Sun 8 Nov | Voorhout 23:19Partial coverage | +2 min | +2 min |
| Sat 7 Nov | Voorhout 23:18Partial coverage | 0 min | — |
| Fri 6 Nov | — 23:09 | 0 min | — |
| Thu 5 Nov | — 23:09 | No data | — |
| Wed 4 Nov | — 23:09 | 0 min | — |
| Mon 2 Nov | — 23:09 | 0 min | — |
| Sun 1 Nov | Voorhout 23:19Partial coverage | 0 min | — |
| Sat 31 Oct | Voorhout 23:18 | No data | — |
| Fri 30 Oct | — 23:11 | No data | — |
| Thu 29 Oct | — 23:11 | 0 min | — |
| Wed 28 Oct | — 23:11 | No data | — |
| Tue 27 Oct | — 23:18 | No data | — |
| Mon 26 Oct | — 23:11 | No data | — |
| Sun 25 Oct | Voorhout 23:20 | No data | — |
| Sat 24 Oct | — 23:12 | No data | — |
| Fri 23 Oct | — 23:11 | 0 min | — |
| Thu 22 Oct | — 23:12 | No data | — |
| Wed 21 Oct | — 23:11 | No data | — |
| Tue 20 Oct | — 23:12 | No data | — |
| Mon 19 Oct | — 23:11 | No data | — |