Train NS 184881 Beverwijk – Hoorn
✓ Today’s run finished
Today, last fix heading to — at 00:54 +1 min
- Beverwijk00:02
- Uitgeest00:10
- Castricum00:20
- Alkmaar00:30
- Alkmaar Noord00:34
- Obdam00:44
- Hoorn00:54
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 so far)
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
Distribution · 90 days
3 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 3
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- 100% T n=1
- 100% F n=1
- 100% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 00:02 | |
| 00:06 | |
| 00:10 / 00:15 | |
| 00:20 | |
| 00:25 | |
| 00:30 / 00:31 | |
| 00:34 | |
| 00:39 | |
| 00:44 / 00:45 | |
| 00:54 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | — 00:54 | +1 min | — |
| Fri 6 Nov | — 00:29 | 0 min | — |
| Thu 5 Nov | — 00:29 | 0 min | — |