Train NS 4184 Hoofddorp – Hoorn
✓ Today’s run finished
Today, last fix heading to — at 01:14 +3 min
- Hoofddorp00:13
- Amsterdam Lelylaan00:25
- Amsterdam Sloterdijk00:29
- Zaandam Kogerveld00:43
- Purmerend Weidevenne00:49
- Purmerend Overwhere00:55
- Hoorn01:06
Next service: tomorrow 00:13 from Hoofddorp · Sun 15 Nov
Last 30 days
Arrival delay at Hoorn, 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 24 Oct Max en route +5 min · last fix heading to — +5 min
- Mon 9 Nov Max en route +4 min · last fix heading to Purmerend Overwhere +4 min
- Sat 14 Nov Max en route +5 min · last fix heading to — +3 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 31
- 3–10 min 9% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 100% T n=6
- 100% W n=6
- 100% T n=6
- 100% F n=5
- 67% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 34 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 |
|---|---|---|---|
| 00:13 | on time | on time | |
| 00:17 / 00:18 | ≈ on time | ≈ on time | |
| 00:25 | ≈ on time | ≈ on time | |
| 00:29 / 00:32 | ≈ on time | ≈ +1 min | |
| 00:38 | ≈ on time | ≈ +1 min | |
| 00:43 | ≈ on time | ≈ +1 min | |
| 00:49 | ≈ on time | ≈ +1 min | |
| 00:52 | ≈ on time | ≈ +1 min | |
| 00:55 | ≈ on time | ≈ +2 min | |
| 01:06 | 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 |
|---|---|---|---|
| Sat 14 Nov | — 01:14 | +3 min | +5 min |
| Fri 13 Nov | — 01:04 | 0 min | — |
| Thu 12 Nov | — 01:04 | 0 min | — |
| Wed 11 Nov | — 01:07 | 0 min | — |
| Tue 10 Nov | — 01:08 | 0 min | — |
| Mon 9 Nov | Purmerend Overwhere 01:14 | +4 min | +4 min |
| Sun 8 Nov | — 01:08 | 0 min | — |
| Sat 7 Nov | — 01:08 | +2 min | +2 min |
| Fri 6 Nov | — 01:04 | 0 min | — |
| Thu 5 Nov | — 01:04 | 0 min | — |
| Wed 4 Nov | — 01:09 | 0 min | — |
| Tue 3 Nov | — 01:07 | 0 min | — |
| Sun 1 Nov | Purmerend Overwhere 01:09Partial coverage | 0 min | — |
| Sat 31 Oct | — 01:07 | 0 min | — |
| Thu 29 Oct | — 01:04 | 0 min | — |
| Wed 28 Oct | — 01:06 | 0 min | — |
| Tue 27 Oct | — 01:09 | 0 min | — |
| Sun 25 Oct | Purmerend Overwhere 01:09 | No data | — |
| Sat 24 Oct | — 01:18 | +5 min | +5 min |
| Fri 23 Oct | — 01:04 | 0 min | — |
| Thu 22 Oct | — 01:04 | 0 min | — |
| Wed 21 Oct | — 01:11 | 0 min | — |
| Tue 20 Oct | — 01:50 | 0 min | — |
| Sun 18 Oct | Purmerend Overwhere 01:10Partial coverage | 0 min | — |
| Sat 17 Oct | Purmerend Overwhere 01:08 | 0 min | — |
| Fri 16 Oct | — 01:15 | 0 min | — |
| Thu 15 Oct | — 01:07 | 0 min | — |
| Wed 14 Oct | — 01:07 | 0 min | — |
| Tue 13 Oct | — 01:10 | 0 min | — |
| Sun 11 Oct | Purmerend Overwhere 01:26 | 0 min | — |