Train NS 184883 Beverwijk – Alkmaar
✓ Today’s run finished
Today, last fix heading to — at 00:59 0 min
- Beverwijk00:32
- Heemskerk00:36
- Uitgeest00:40
- Castricum00:50
- Heiloo00:55
- Alkmaar01:00
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%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 2 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
Last 30 days
Arrival delay at Alkmaar, 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
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 4
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — 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 (6 stops).
Not enough runs yet to work out the usual delay by stop.
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:59 | 0 min | — |
| Fri 6 Nov | — 00:59 | 0 min | — |
| Thu 5 Nov | — 00:59 | 0 min | — |
| Mon 5 Oct | Haarlem 01:01 | 0 min | — |
| Sun 4 Oct | Heemskerk 00:49 | No data | — |
| Mon 24 Aug | Heiloo 01:16 | No data | — |