Train NS 704046 Hoofddorp – Uitgeest
It does not run today
Last recorded run: Monday 5 October 0 min
Next service: tomorrow 14:52 from Hoofddorp · Sun 11 Oct
Next departure 14:52 tomorrow · Hoofddorp
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 Uitgeest, 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 (10 stops).
| Stop | Sched. |
|---|---|
| 14:52 | |
| 14:57 / 14:59 | |
| 15:06 | |
| 15:09 / 15:18 | |
| 15:25 | |
| 15:28 | |
| 15:30 | |
| 15:33 / 15:34 | |
| 15:37 | |
| 15:42 |
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 | Krommenie-Assendelft 15:54Partial coverage | 0 min | — |
| Sun 4 Oct | Obdam 16:30 | No data | — |
| Sat 3 Oct | Obdam 16:29 | No data | — |