Train NS 704071 Uitgeest – Amsterdam Centraal
It does not run today
Last recorded run: Sunday 1 November +2 min
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 0 full · 2 partial · 0 no data
On-time · 90 days
100%
3/3 runs under 3 min
RT coverage: 1 full · 2 partial · 2 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 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
3 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 3
- 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
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 18:18 | |
| 18:22 | |
| 18:26 | |
| 18:29 | |
| 18:32 | |
| 18:35 | |
| 18:41 | |
| 18:47 |
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 1 Nov | Amsterdam Sloterdijk 18:54Partial coverage | +2 min | +2 min |
| Sun 11 Oct | Amsterdam Sloterdijk 18:55Partial coverage | 0 min | — |
| Mon 5 Oct | — 19:03 | 0 min | — |
| Sun 4 Oct | Zaandam 18:49 | No data | — |
| Sat 3 Oct | Schiphol Airport 19:07 | No data | — |