Train NS 18178
It does not run today
Last recorded run: Monday 5 October +3 min
The mini-map returns when the train runs
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
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
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
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | โ 23:00 | +3 min | +3 min |
| Sun 4 Oct | Amsterdam Sloterdijk 23:11 | No data | โ |
| Sun 27 Sept | Amsterdam Sloterdijk 23:04 | 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.