Train NS 4159 Hoorn Kersenboogerd – Hoofddorp
✓ Today’s run finished
Today, last fix heading to Zaandam at 16:04 0 min
- Hoorn Kersenboogerd15:18
- Purmerend Overwhere15:35
- Purmerend15:37
- Zaandam Kogerveld15:47
- Zaandam15:50
- Amsterdam Sloterdijk15:56
- Hoofddorp16:22
Next service: tomorrow 15:18 from Hoorn Kersenboogerd · Sun 8 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
- Sat 10 Oct Max en route +3 min · last fix heading to Schiphol Airport +3 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 16
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=2
- 100% T n=1
- 100% F n=1
- 80% S n=5
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 17 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:18 | on time | on time | |
| 15:22 / 15:23 | ≈ on time | ≈ on time | |
| 15:35 | ≈ on time | ≈ on time | |
| 15:37 | ≈ on time | ≈ on time | |
| 15:40 | ≈ on time | ≈ on time | |
| 15:47 | ≈ on time | ≈ +1 min | |
| 15:50 | ≈ on time | ≈ +1 min | |
| 15:56 / 16:06 | ≈ on time | ≈ +1 min | |
| 16:10 | ≈ on time | ≈ +1 min | |
| 16:16 / 16:17 | ≈ on time | ≈ +1 min | |
| 16:22 | on time | +1 min |
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 | Zaandam 16:04Partial coverage | 0 min | — |
| Fri 6 Nov | Schiphol Airport 16:29 | No data | — |
| Thu 5 Nov | Schiphol Airport 16:30 | No data | — |
| Wed 4 Nov | Schiphol Airport 16:32 | 0 min | — |
| Tue 3 Nov | Schiphol Airport 16:29 | No data | — |
| Mon 2 Nov | Schiphol Airport 16:34 | 0 min | — |
| Sun 1 Nov | Schiphol Airport 16:32Partial coverage | 0 min | — |
| Sat 31 Oct | Schiphol Airport 16:32Partial coverage | 0 min | — |
| Fri 30 Oct | Schiphol Airport 16:31 | No data | — |
| Thu 29 Oct | Schiphol Airport 16:31 | No data | — |
| Wed 28 Oct | Schiphol Airport 16:31 | No data | — |
| Tue 27 Oct | Schiphol Airport 16:32 | 0 min | — |
| Mon 26 Oct | Schiphol Airport 16:31 | No data | — |
| Sun 25 Oct | Schiphol Airport 16:31 | No data | — |
| Sat 24 Oct | Schiphol Airport 16:31Partial coverage | 0 min | — |
| Fri 23 Oct | Schiphol Airport 16:31 | No data | — |
| Thu 22 Oct | Schiphol Airport 16:31 | No data | — |
| Wed 21 Oct | Schiphol Airport 16:37 | No data | — |
| Tue 20 Oct | Schiphol Airport 16:31 | No data | — |
| Mon 19 Oct | Schiphol Airport 16:32 | No data | — |
| Sun 18 Oct | Schiphol Airport 16:31 | +1 min | +1 min |
| Sat 17 Oct | Schiphol Airport 16:31 | 0 min | — |
| Fri 16 Oct | Schiphol Airport 16:31 | No data | — |
| Thu 15 Oct | Schiphol Airport 16:31 | No data | — |
| Wed 14 Oct | Schiphol Airport 16:31 | No data | — |
| Tue 13 Oct | Schiphol Airport 16:31 | No data | — |
| Mon 12 Oct | Schiphol Airport 16:32 | 0 min | — |
| Sun 11 Oct | Schiphol Airport 16:31Partial coverage | 0 min | — |
| Sat 10 Oct | Schiphol Airport 16:31Partial coverage | +3 min | +3 min |
| Fri 9 Oct | Schiphol Airport 16:31Partial coverage | 0 min | — |