Train NS 4153 Hoorn Kersenboogerd – Hoofddorp
✓ Today’s run finished
Today, last fix heading to Zaandam at 14:34 0 min
- Hoorn Kersenboogerd13:54
- Purmerend Overwhere14:09
- Purmerend14:12
- Zaandam Kogerveld14:21
- Zaandam14:25
- Amsterdam Sloterdijk14:31
- Hoofddorp14:52
Next service: tomorrow 13:54 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 31 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 19
- 3–10 min 5% · 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=3
- 100% T n=2
- 100% F n=4
- 75% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 20 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 |
|---|---|---|---|
| 13:54 | on time | on time | |
| 13:57 / 13:58 | ≈ on time | ≈ on time | |
| 14:09 | ≈ on time | ≈ +1 min | |
| 14:12 | ≈ on time | ≈ +1 min | |
| 14:15 | ≈ on time | ≈ +1 min | |
| 14:21 | ≈ on time | ≈ +1 min | |
| 14:25 | ≈ on time | ≈ +2 min | |
| 14:31 / 14:36 | ≈ on time | ≈ +2 min | |
| 14:40 | ≈ on time | ≈ +2 min | |
| 14:46 / 14:47 | ≈ on time | ≈ +3 min | |
| 14:52 | on time | +3 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 14:34 | 0 min | — |
| Fri 6 Nov | Schiphol Airport 14:59 | No data | — |
| Thu 5 Nov | Schiphol Airport 14:59 | No data | — |
| Wed 4 Nov | Schiphol Airport 14:59Partial coverage | 0 min | — |
| Tue 3 Nov | Schiphol Airport 15:03 | No data | — |
| Mon 2 Nov | Schiphol Airport 14:59Partial coverage | 0 min | — |
| Sun 1 Nov | Schiphol Airport 15:02 | 0 min | — |
| Sat 31 Oct | Schiphol Airport 15:03 | +4 min | +4 min |
| Fri 30 Oct | Schiphol Airport 15:01 | 0 min | — |
| Thu 29 Oct | Schiphol Airport 15:02Partial coverage | 0 min | — |
| Wed 28 Oct | Schiphol Airport 15:02Partial coverage | 0 min | — |
| Tue 27 Oct | Schiphol Airport 15:01 | No data | — |
| Mon 26 Oct | Schiphol Airport 15:01 | No data | — |
| Sun 25 Oct | Schiphol Airport 15:01 | No data | — |
| Sat 24 Oct | Schiphol Airport 15:03 | +1 min | +1 min |
| Fri 23 Oct | Schiphol Airport 15:03 | 0 min | — |
| Thu 22 Oct | Schiphol Airport 15:01 | No data | — |
| Wed 21 Oct | Schiphol Airport 15:01 | No data | — |
| Tue 20 Oct | Schiphol Airport 15:01Partial coverage | 0 min | — |
| Mon 19 Oct | Schiphol Airport 15:01 | No data | — |
| Sun 18 Oct | Schiphol Airport 15:02 | +1 min | +1 min |
| Sat 17 Oct | Schiphol Airport 15:01 | No data | — |
| Fri 16 Oct | Schiphol Airport 15:02 | 0 min | — |
| Thu 15 Oct | Schiphol Airport 15:02 | No data | — |
| Wed 14 Oct | Schiphol Airport 15:01 | No data | — |
| Tue 13 Oct | Schiphol Airport 15:01 | No data | — |
| Mon 12 Oct | Schiphol Airport 15:01Partial coverage | 0 min | — |
| Sun 11 Oct | Hoorn 14:53 | No data | — |
| Sat 10 Oct | Schiphol Airport 15:01 | 0 min | — |
| Fri 9 Oct | Schiphol Airport 15:04 | +3 min | +3 min |