Train NS 704060 Hoofddorp – Uitgeest
It does not run today
Last recorded run: Monday 5 October +6 min
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 1 full · 0 partial · 2 no data
On-time · 90 days
—
Too little data (1/3 runs with data)
RT coverage: 1 full · 0 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 Uitgeest, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 5 Oct Max en route +7 min · last fix heading to — +6 min
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 0% · 0
- 3–10 min 100% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% 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 (10 stops).
| Stop | Sched. |
|---|---|
| 18:22 | |
| 18:27 / 18:29 | |
| 18:36 | |
| 18:40 / 18:48 | |
| 18:55 | |
| 18:58 | |
| 19:00 | |
| 19:03 / 19:04 | |
| 19:07 | |
| 19:12 |
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 | — 19:20 | +6 min | +7 min |
| Sun 4 Oct | Obdam 19:59 | No data | — |
| Sat 3 Oct | Obdam 19:59 | No data | — |