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