Train NS 4248 Den Haag Centraal – Amsterdam Centraal
It has not run yet today
Last recorded run: Friday 6 November 0 min
Next service: today 15:55 from Den Haag Centraal · Sat 7 Nov
Last 30 days
Arrival delay at Amsterdam 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
- Thu 8 Oct Max en route +5 min · last fix heading to Heemstede-Aerdenhout +4 min
- Sat 31 Oct Max en route +4 min · last fix heading to Heemstede-Aerdenhout +3 min
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 5% · 1
- On time 86% · 18
- 3–10 min 10% · 2
- 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
- 67% T n=3
- 100% F n=4
- 75% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 21 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 |
|---|---|---|---|
| 15:55 | on time | on time | |
| 15:58 | ≈ on time | ≈ on time | |
| 16:01 | ≈ on time | ≈ on time | |
| 16:06 | ≈ on time | ≈ on time | |
| 16:10 | ≈ on time | ≈ on time | |
| 16:14 / 16:21 | ≈ on time | ≈ on time | |
| 16:26 | ≈ on time | ≈ +1 min | |
| 16:34 | ≈ on time | ≈ +1 min | |
| 16:40 | ≈ on time | ≈ +1 min | |
| 16:45 / 16:47 | ≈ on time | ≈ +1 min | |
| 16:50 | ≈ on time | ≈ +1 min | |
| 16:55 | ≈ on time | ≈ +1 min | |
| 17:00 | ≈ on time | ≈ +2 min | |
| 17:05 | on time | +2 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 |
|---|---|---|---|
| Fri 6 Nov | Amsterdam Sloterdijk 17:14Partial coverage | 0 min | — |
| Thu 5 Nov | Amsterdam Sloterdijk 17:14 | No data | — |
| Wed 4 Nov | Amsterdam Sloterdijk 17:14 | 0 min | — |
| Tue 3 Nov | Amsterdam Sloterdijk 17:14 | No data | — |
| Mon 2 Nov | Amsterdam Sloterdijk 17:14 | No data | — |
| Sun 1 Nov | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Sat 31 Oct | Heemstede-Aerdenhout 16:55 | +3 min | +4 min |
| Fri 30 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Thu 29 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Wed 28 Oct | Heemstede-Aerdenhout 16:48 | 0 min | — |
| Tue 27 Oct | Heemstede-Aerdenhout 16:53 | No data | — |
| Mon 26 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Sun 25 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Sat 24 Oct | Heemstede-Aerdenhout 16:52 | +1 min | — |
| Fri 23 Oct | Heemstede-Aerdenhout 16:53 | 0 min | — |
| Thu 22 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Wed 21 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Tue 20 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Mon 19 Oct | Heemstede-Aerdenhout 16:54 | 0 min | — |
| Sun 18 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Sat 17 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Fri 16 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Thu 15 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Wed 14 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Tue 13 Oct | Heemstede-Aerdenhout 16:52 | No data | — |
| Mon 12 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Fri 9 Oct | Heemstede-Aerdenhout 16:53 | +1 min | +1 min |
| Thu 8 Oct | Heemstede-Aerdenhout 16:55 | +4 min | +5 min |
| Wed 7 Oct | Heemstede-Aerdenhout 16:52 | 0 min | — |
| Tue 6 Oct | Heemstede-Aerdenhout 16:52 | +1 min | — |