Train NS 8155 Amsterdam Centraal → Hoofddorp
NS 8155 Amsterdam Centraal–Hoofddorp: final delay under 3 min on 16 of its 17 runs with data in the last 30 days (94%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:22 (GMT+1).
An alert on this phone or computer when the 8155 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November 0 min
Next service: tomorrow 15:05 from Amsterdam Centraal · Mon 23 Nov
Last 30 days
Arrival delay at Hoofddorp, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 8 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 23
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=5
- 100% W n=5
- 100% T n=3
- 100% F n=3
- 100% S n=2
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 24 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 15:05 | on time | on time | |
| 15:10 | — | — | |
| 15:14 | — | — | |
| 15:20 / 15:23 | — | — | |
| 15:27 | — | — |
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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Thu 19 Nov | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Wed 18 Nov | Schiphol Airport 15:37Partial coverage | +3 min | +3 min |
| Tue 17 Nov | Schiphol Airport 15:37Partial coverage | +1 min | +1 min |
| Mon 16 Nov | Schiphol Airport 15:38Partial coverage | 0 min | — |
| Fri 13 Nov | Schiphol Airport 15:34Partial coverage | +1 min | +1 min |
| Thu 12 Nov | Schiphol Airport 15:37Partial coverage | +2 min | +2 min |
| Wed 11 Nov | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Tue 10 Nov | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Mon 9 Nov | Schiphol Airport 15:38Partial coverage | 0 min | — |
| Sun 8 Nov | Schiphol Airport 15:39Partial coverage | +4 min | +4 min |
| Sat 7 Nov | — 15:28 | No data | — |
| Fri 6 Nov | Schiphol Airport 15:37 | No data | — |
| Thu 5 Nov | Schiphol Airport 15:37 | No data | — |
| Wed 4 Nov | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Tue 3 Nov | Schiphol Airport 15:39 | No data | — |
| Mon 2 Nov | Schiphol Airport 15:53 | No data | — |
| Sun 1 Nov | Schiphol Airport 15:38Partial coverage | 0 min | — |
| Sat 31 Oct | Schiphol Airport 15:39Partial coverage | +2 min | +2 min |
| Fri 30 Oct | Schiphol Airport 15:37 | No data | — |
| Thu 29 Oct | Schiphol Airport 15:37 | No data | — |
| Wed 28 Oct | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Tue 27 Oct | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Mon 26 Oct | Schiphol Airport 15:37 | No data | — |
| Sun 25 Oct | Schiphol Airport 15:37 | No data | — |
| Sat 24 Oct | Schiphol Airport 15:37Partial coverage | 0 min | — |
| Fri 23 Oct | Schiphol Airport 15:38 | No data | — |
| Thu 22 Oct | Schiphol Airport 15:37 | No data | — |
| Wed 21 Oct | Schiphol Airport 15:37 | No data | — |
| Tue 20 Oct | Schiphol Airport 15:37Partial coverage | 0 min | — |