Train NS 4820 Hoorn – Beverwijk
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 08:06 from Hoorn · Thu 5 Nov
Last 30 days
Arrival delay at Beverwijk, 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 17 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min
- Tue 6 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min
Distribution · 90 days
25 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 23
- 3–10 min 8% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 67% T n=3
- 100% W n=5
- 100% T n=4
- 100% F n=3
- 75% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 25 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 |
|---|---|---|---|
| 08:06 | on time | on time | |
| 08:14 / 08:15 | ≈ on time | ≈ on time | |
| 08:21 | ≈ on time | ≈ +1 min | |
| 08:26 | ≈ on time | ≈ +1 min | |
| 08:29 / 08:32 | ≈ on time | ≈ +1 min | |
| 08:37 | ≈ on time | ≈ +1 min | |
| 08:43 | ≈ on time | ≈ +1 min | |
| 08:48 | ≈ on time | ≈ +2 min | |
| 08:52 | ≈ on time | ≈ +2 min | |
| 08:56 | 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 |
|---|---|---|---|
| Wed 4 Nov | Heemskerk 09:07Partial coverage | 0 min | — |
| Tue 3 Nov | Heemskerk 09:04 | No data | — |
| Mon 2 Nov | Heemskerk 09:07 | No data | — |
| Sun 1 Nov | Amsterdam Sloterdijk 09:46 | +1 min | +2 min |
| Sat 31 Oct | Amsterdam Sloterdijk 09:46 | +1 min | +2 min |
| Fri 30 Oct | Amsterdam Sloterdijk 09:45 | 0 min | — |
| Thu 29 Oct | Amsterdam Sloterdijk 09:47 | 0 min | — |
| Wed 28 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Tue 27 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Mon 26 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Sun 25 Oct | Amsterdam Sloterdijk 09:45 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Fri 23 Oct | Amsterdam Sloterdijk 09:45 | 0 min | — |
| Thu 22 Oct | Amsterdam Sloterdijk 09:45 | 0 min | — |
| Wed 21 Oct | Amsterdam Sloterdijk 09:50 | 0 min | — |
| Tue 20 Oct | Amsterdam Sloterdijk 09:45 | 0 min | — |
| Mon 19 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Sun 18 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Sat 17 Oct | Amsterdam Sloterdijk 09:47 | +4 min | +4 min |
| Fri 16 Oct | Amsterdam Sloterdijk 09:44 | No data | — |
| Thu 15 Oct | Amsterdam Sloterdijk 10:58 | 0 min | — |
| Wed 14 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Tue 13 Oct | Amsterdam Sloterdijk 09:44 | No data | — |
| Mon 12 Oct | Amsterdam Sloterdijk 09:47 | 0 min | — |
| Sun 11 Oct | Amsterdam Sloterdijk 09:46 | +2 min | +2 min |
| Sat 10 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Fri 9 Oct | Amsterdam Sloterdijk 09:47 | +2 min | +2 min |
| Thu 8 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Wed 7 Oct | Amsterdam Sloterdijk 09:44 | 0 min | — |
| Tue 6 Oct | Amsterdam Sloterdijk 09:48 | +4 min | +4 min |