Train NS 4156 Hoofddorp – Hoorn Kersenboogerd
✓ Today’s run finished
Today, last fix heading to Hoorn at 18:18 No data
- Hoofddorp17:08
- Amsterdam Lelylaan17:20
- Amsterdam Sloterdijk17:24
- Zaandam Kogerveld17:38
- Purmerend17:48
- Hoorn18:02
- Hoorn Kersenboogerd18:07
Next service: tomorrow 17:08 from Hoofddorp · Fri 6 Nov
Last 30 days
Arrival delay at Hoorn Kersenboogerd, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 7 Oct Max en route +9 min · last fix heading to Hoorn +8 min
- Tue 6 Oct Max en route +7 min · last fix heading to Hoorn +5 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 16
- 3–10 min 11% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 0% T n=1
- 67% W n=3
- 100% T n=1
- 100% F n=2
- 100% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 18 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:08 | on time | on time | |
| 17:12 / 17:13 | ≈ on time | ≈ on time | |
| 17:20 | ≈ on time | ≈ on time | |
| 17:24 / 17:28 | ≈ on time | ≈ on time | |
| 17:34 | ≈ on time | ≈ on time | |
| 17:38 | ≈ on time | ≈ on time | |
| 17:45 | ≈ on time | ≈ on time | |
| 17:48 | ≈ on time | ≈ on time | |
| 17:50 | ≈ on time | ≈ on time | |
| 18:02 / 18:04 | ≈ on time | ≈ +1 min | |
| 18:07 | 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 |
|---|---|---|---|
| Thu 5 Nov | Hoorn 18:18 | No data | — |
| Wed 4 Nov | Hoorn 18:18Partial coverage | 0 min | — |
| Tue 3 Nov | Hoorn 18:19 | No data | — |
| Mon 2 Nov | Hoorn 18:18Partial coverage | 0 min | — |
| Sun 1 Nov | Hoorn 18:23 | +1 min | — |
| Sat 31 Oct | Hoorn 18:22 | 0 min | — |
| Fri 30 Oct | Hoorn 18:22 | No data | — |
| Thu 29 Oct | Purmerend Overwhere 18:14 | No data | — |
| Wed 28 Oct | Hoorn 18:18Partial coverage | 0 min | — |
| Tue 27 Oct | Hoorn 18:18 | No data | — |
| Mon 26 Oct | Hoorn 18:18Partial coverage | +1 min | +1 min |
| Sun 25 Oct | Hoorn 18:22 | No data | — |
| Sat 24 Oct | Hoorn 18:22 | 0 min | — |
| Fri 23 Oct | Hoorn 18:23 | 0 min | — |
| Thu 22 Oct | Hoorn 18:18 | No data | — |
| Wed 21 Oct | Hoorn 18:18 | No data | — |
| Tue 20 Oct | Hoorn 18:18 | No data | — |
| Mon 19 Oct | Hoorn 18:18 | No data | — |
| Sun 18 Oct | Hoorn 18:22 | +1 min | +1 min |
| Sat 17 Oct | Hoorn 18:23 | 0 min | — |
| Fri 16 Oct | Hoorn 18:22 | No data | — |
| Thu 15 Oct | Hoorn 18:18 | No data | — |
| Wed 14 Oct | Hoorn 18:22 | No data | — |
| Tue 13 Oct | Hoorn 18:18 | No data | — |
| Mon 12 Oct | Hoorn 18:18Partial coverage | 0 min | — |
| Sun 11 Oct | Hoorn 18:22 | 0 min | — |
| Sat 10 Oct | Hoorn 18:22 | 0 min | — |
| Fri 9 Oct | Hoorn 18:22 | 0 min | — |
| Thu 8 Oct | Purmerend Overwhere 18:10Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Hoorn 18:18Partial coverage | +8 min | +9 min |