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