Train NS 4866 Alkmaar – Amsterdam Centraal
Running now · updated 20:47
Heading to Amsterdam Centraal 0 min
Estimated arrival at Amsterdam Centraal 21:05 · 3 km/h
- Alkmaar20:00
- Castricum20:10
- Beverwijk20:27
- Santpoort Noord20:36
- Bloemendaal20:42
- Halfweg-Zwanenburg20:55
- Amsterdam Centraal21:05
Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 18 runs arrived on time.
Last 30 days
Arrival delay at Amsterdam Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 5 Oct Max en route +4 min · last fix heading to — +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 96% · 24
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=2
- 100% W n=4
- 100% T n=4
- 100% F n=5
- 100% S n=4
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 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 | Today |
|---|---|---|---|---|
| 20:00 | on time | on time | ||
| 20:05 | ≈ on time | ≈ on time | ||
| 20:10 | ≈ on time | ≈ on time | ||
| 20:15 / 20:20 | ≈ on time | ≈ on time | ||
| 20:24 | ≈ on time | ≈ on time | ||
| 20:27 / 20:28 | ≈ on time | ≈ on time | ||
| 20:33 | ≈ on time | ≈ +1 min | ||
| 20:36 | ≈ on time | ≈ +1 min | ||
| 20:39 | ≈ on time | ≈ +1 min | ||
| 20:42 | ≈ on time | ≈ +1 min | ||
| 20:46 / 20:47 | ≈ on time | ≈ +1 min | ||
| 20:50 | ≈ on time | ≈ +1 min | ||
| 20:55 | ≈ on time | ≈ +1 min | ||
| 21:00 | ≈ on time | ≈ +1 min | ||
| 21:05 | on time | +1 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 |
|---|---|---|---|
| Fri 13 Nov | — 20:44 | 0 min | — |
| Thu 12 Nov | — 20:52 | 0 min | — |
| Wed 11 Nov | — 21:04 | 0 min | — |
| Tue 10 Nov | — 21:04 | 0 min | — |
| Mon 9 Nov | — 21:04 | 0 min | — |
| Sun 8 Nov | Amsterdam Sloterdijk 21:14 | 0 min | +1 min |
| Sat 7 Nov | Amsterdam Sloterdijk 21:14 | 0 min | — |
| Fri 6 Nov | — 20:27 | 0 min | — |
| Thu 5 Nov | — 20:28 | No data | — |
| Wed 4 Nov | — 20:28 | 0 min | — |
| Mon 2 Nov | — 20:27 | No data | — |
| Sun 1 Nov | Amsterdam Sloterdijk 21:14 | 0 min | — |
| Sat 31 Oct | Amsterdam Sloterdijk 21:15 | 0 min | — |
| Thu 29 Oct | — 21:06 | 0 min | — |
| Wed 28 Oct | — 21:06 | No data | — |
| Tue 27 Oct | — 21:07 | No data | — |
| Mon 26 Oct | Heerhugowaard 21:06 | No data | — |
| Sun 25 Oct | Amsterdam Sloterdijk 21:15 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 21:15 | 0 min | — |
| Fri 23 Oct | — 21:07 | +1 min | — |
| Thu 22 Oct | — 21:07 | No data | — |
| Wed 21 Oct | — 21:07 | 0 min | — |
| Tue 20 Oct | — 21:08 | No data | — |
| Mon 19 Oct | — 21:07 | No data | — |
| Sun 18 Oct | Amsterdam Sloterdijk 21:16 | +2 min | +2 min |
| Sat 17 Oct | Amsterdam Sloterdijk 21:14 | No data | — |
| Fri 16 Oct | — 21:07 | +1 min | — |
| Thu 15 Oct | — 21:09 | 0 min | — |
| Wed 14 Oct | Hoorn 21:07 | No data | — |
| Tue 13 Oct | — 21:07 | No data | — |