Train NS 18148 Hoofddorp – Amsterdam Centraal
It does not run today
Last recorded run: Monday 5 October +1 min
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 0 full · 1 partial · 2 no data
On-time · 90 days
—
Too little data (1/3 runs with data)
RT coverage: 0 full · 1 partial · 2 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 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
Distribution · 90 days
1 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 1
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
| Stop | Sched. |
|---|---|
| 15:02 | |
| 15:07 / 15:08 | |
| 15:15 | |
| 15:19 | |
| 15:25 |
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 |
|---|---|---|---|
| Mon 5 Oct | Amsterdam Sloterdijk 15:34Partial coverage | +1 min | +1 min |
| Sun 4 Oct | Amsterdam Sloterdijk 15:40 | No data | — |
| Sun 27 Sept | Amsterdam Sloterdijk 15:35 | No data | — |