Train NS 8158 Hoofddorp – Amsterdam Centraal
✓ Today’s run finished
Today, last fix heading to — at 17:54 No data
- Hoofddorp17:32
- Schiphol Airport17:37
- Amsterdam Lelylaan17:45
- Amsterdam Sloterdijk17:49
- Amsterdam Centraal17:55
Next service: tomorrow 17:32 from Hoofddorp · Sun 8 Nov
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
Worst days
- Tue 6 Oct Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min
- Fri 9 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min
- Wed 7 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 77% · 10
- 3–10 min 23% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 50% T n=2
- 50% W n=2
- 100% T n=1
- 50% F n=2
- 100% S n=2
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 17:32 | on time | on time | |
| 17:37 / 17:39 | — | — | |
| 17:45 | — | — | |
| 17:49 | — | — | |
| 17:55 | — | — |
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 |
|---|---|---|---|
| Sat 7 Nov | — 17:54 | No data | — |
| Fri 6 Nov | Amsterdam Sloterdijk 18:03Partial coverage | 0 min | — |
| Thu 5 Nov | Amsterdam Sloterdijk 18:03 | No data | — |
| Wed 4 Nov | Amsterdam Sloterdijk 18:03 | No data | — |
| Tue 3 Nov | Amsterdam Sloterdijk 18:03 | No data | — |
| Mon 2 Nov | Amsterdam Sloterdijk 18:03 | No data | — |
| Sun 1 Nov | Amsterdam Sloterdijk 18:04Partial coverage | +1 min | — |
| Sat 31 Oct | Amsterdam Sloterdijk 18:04Partial coverage | 0 min | — |
| Fri 30 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Thu 29 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Wed 28 Oct | Amsterdam Sloterdijk 18:03Partial coverage | 0 min | — |
| Tue 27 Oct | Amsterdam Sloterdijk 18:12 | No data | — |
| Mon 26 Oct | Amsterdam Sloterdijk 18:03Partial coverage | +1 min | +1 min |
| Sun 25 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 18:05Partial coverage | +1 min | — |
| Fri 23 Oct | Amsterdam Sloterdijk 18:04 | No data | — |
| Thu 22 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Wed 21 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Tue 20 Oct | Amsterdam Sloterdijk 18:03Partial coverage | 0 min | — |
| Mon 19 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Sun 18 Oct | Amsterdam Sloterdijk 18:05 | +1 min | +1 min |
| Sat 17 Oct | Amsterdam Sloterdijk 18:10 | No data | — |
| Fri 16 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Thu 15 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Wed 14 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Tue 13 Oct | Amsterdam Sloterdijk 18:03 | No data | — |
| Mon 12 Oct | Amsterdam Sloterdijk 18:07Partial coverage | 0 min | — |
| Fri 9 Oct | Amsterdam Sloterdijk 18:03Partial coverage | +3 min | +3 min |
| Thu 8 Oct | Amsterdam Sloterdijk 17:58Partial coverage | 0 min | — |
| Wed 7 Oct | Amsterdam Sloterdijk 18:03Partial coverage | +3 min | +3 min |