Train NS 4808 Alkmaar – Beverwijk
✓ Today’s run finished
Today, last fix heading to Heemskerk at 06:08 +1 min
- Alkmaar05:30
- Heiloo05:35
- Castricum05:40
- Uitgeest05:44
- Heemskerk05:52
- Beverwijk05:56
Next service: tomorrow 05:30 from Alkmaar · Fri 6 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
- Mon 19 Oct Max en route +14 min · last fix heading to Halfweg-Zwanenburg +14 min
- Thu 8 Oct Max en route +10 min · last fix heading to Amsterdam Sloterdijk +10 min
- Sat 31 Oct Max en route +9 min · last fix heading to Amsterdam Sloterdijk +9 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 27
- 3–10 min 3% · 1
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=5
- 100% W n=5
- 80% T n=5
- 100% F n=4
- 75% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 30 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 |
|---|---|---|---|
| 05:30 | on time | on time | |
| 05:35 | ≈ on time | ≈ +1 min | |
| 05:40 | ≈ on time | ≈ +1 min | |
| 05:44 / 05:48 | ≈ on time | ≈ +2 min | |
| 05:52 | ≈ on time | ≈ +3 min | |
| 05:56 | on time | +3 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 |
|---|---|---|---|
| Thu 5 Nov | Heemskerk 06:08Partial coverage | +1 min | +1 min |
| Wed 4 Nov | Heemskerk 06:07 | 0 min | — |
| Tue 3 Nov | Heemskerk 06:07 | +1 min | — |
| Mon 2 Nov | Heemskerk 06:07 | 0 min | — |
| Sun 1 Nov | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Sat 31 Oct | Amsterdam Sloterdijk 06:53 | +9 min | +9 min |
| Fri 30 Oct | Amsterdam Sloterdijk 06:45 | +1 min | — |
| Thu 29 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Wed 28 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Tue 27 Oct | Amsterdam Sloterdijk 06:45 | +1 min | — |
| Mon 26 Oct | Amsterdam Sloterdijk 06:45 | +1 min | — |
| Sun 25 Oct | Amsterdam Sloterdijk 06:50 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 06:45 | +1 min | +2 min |
| Fri 23 Oct | Amsterdam Sloterdijk 06:45 | 0 min | — |
| Thu 22 Oct | Amsterdam Sloterdijk 06:45 | +2 min | +2 min |
| Wed 21 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Tue 20 Oct | Amsterdam Sloterdijk 06:46 | +2 min | +2 min |
| Mon 19 Oct | Halfweg-Zwanenburg 07:05 | +14 min | +14 min |
| Sun 18 Oct | Amsterdam Sloterdijk 06:45 | 0 min | — |
| Sat 17 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Fri 16 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Thu 15 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Wed 14 Oct | Amsterdam Sloterdijk 06:44 | 0 min | +4 min |
| Tue 13 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Mon 12 Oct | Amsterdam Sloterdijk 06:45 | 0 min | — |
| Sun 11 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Sat 10 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Fri 9 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |
| Thu 8 Oct | Amsterdam Sloterdijk 06:54 | +10 min | +10 min |
| Wed 7 Oct | Amsterdam Sloterdijk 06:44 | 0 min | — |