Train NS 2178 Haarlem – Amsterdam Centraal
It does not run today
Last recorded run: Saturday 10 October 0 min
Next service: Friday 23:55 from Haarlem · Fri 16 Oct
Next departure 23:55 Friday · Haarlem
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 2 no data
On-time · 90 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 5 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 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
- Sun 9 Aug Max en route +17 min · last fix heading to Amsterdam Sloterdijk +6 min
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 75% · 3
- 3–10 min 25% · 1
- 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
- 100% F n=1
- 100% S n=1
- 50% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
| Stop | Sched. |
|---|---|
| 23:55 | |
| 00:04 | |
| 00:10 |
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 10 Oct | — 00:12 | 0 min | — |
| Fri 9 Oct | — 00:11 | 0 min | — |
| Sat 3 Oct | Haarlem 23:54 | No data | — |
| Sat 26 Sept | Leiden Centraal 23:47 | No data | — |
| Sun 13 Sept | Amsterdam Sloterdijk 00:19 | +1 min | +2 min |
| Sun 23 Aug | Heemstede-Aerdenhout 00:05 | No data | — |
| Sat 22 Aug | Heemstede-Aerdenhout 00:04 | No data | — |
| Sat 15 Aug | Den Haag Centraal 23:21 | No data | — |
| Sun 9 Aug | Amsterdam Sloterdijk 01:00 | +6 min | +17 min |