Train NS 704052 Amsterdam Centraal – Uitgeest
On-time · 30 days
—
Too little data (2/4 runs with data)
RT coverage: 1 full · 1 partial · 2 no data
On-time · 90 days
—
Too little data (2/4 runs with data)
RT coverage: 1 full · 1 partial · 2 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 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 Krommenie-Assendelft +7 min
Distribution · 90 days
2 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 50% · 1
- 3–10 min 50% · 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
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
| Stop | Sched. |
|---|---|
| 16:43 | |
| 16:49 | |
| 16:55 | |
| 16:58 | |
| 17:01 | |
| 17:03 / 17:04 | |
| 17:08 | |
| 17: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 |
|---|---|---|---|
| Sun 11 Oct | Krommenie-Assendelft 17:22Partial coverage | 0 min | — |
| Mon 5 Oct | Krommenie-Assendelft 17:26 | +7 min | +7 min |
| Sun 4 Oct | Obdam 18:00 | No data | — |
| Sat 3 Oct | Obdam 18:00 | No data | — |