Train NS 18216
It does not run today
Last recorded run: Monday 5 October No data
The mini-map returns when the train runs
On-time ยท 30 days
โ
Too little data (0/4 runs with data)
RT coverage: 0 full ยท 0 partial ยท 4 no data
On-time ยท 90 days
โ
Too little data (0/7 runs with data)
RT coverage: 0 full ยท 0 partial ยท 7 no data
Typical delay
โ
Needs at least 5 runs with data (0 so far)
P90
โ
Needs at least 5 runs with data (0 so far)
Last 30 days
Delay at the end of each run, 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
No runs with a known final delay yet.
On-time by weekday
- โ M n=0
- โ T n=0
- โ W n=0
- โ T n=0
- โ F n=0
- โ S n=0
- โ S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | Amsterdam Sloterdijk 07:50 | No data | โ |
| Sun 4 Oct | Amsterdam Sloterdijk 07:32 | No data | โ |
| Sun 27 Sept | Amsterdam Sloterdijk 07:47 | No data | โ |
| Sun 13 Sept | Amsterdam Sloterdijk 07:51 | No data | โ |
| Sat 12 Sept | Schiphol Airport 07:23 | No data | โ |
| Sun 23 Aug | Amsterdam Sloterdijk 07:49 | No data | โ |
| Sat 22 Aug | Amsterdam Sloterdijk 07:49 | No data | โ |
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.