Train NS 4867 Beverwijk – Alkmaar

Beverwijk 20:32 → Alkmaar 21:00 Daily 0 h 28 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 20:32 from Beverwijk · Sat 7 Nov

Next departure 20:32 today · Beverwijk
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

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

Worst days

  • Fri 9 Oct Max en route +8 min · last fix heading to — +7 min

Distribution · 90 days

24 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 80% F n=5
  • 100% S n=3
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 stops).

Last 90 days, 24 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.

StopSched.Usually 9 days in 10
20:32on time on time
20:36≈ on time ≈ on time
20:40 / 20:45≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:55≈ on time ≈ +1 min
21:00on 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

DateLast stopFinalMax
Fri 6 Nov— 21:04+1 min+1 min
Thu 5 Nov— 21:00No data—
Wed 4 Nov— 21:02+1 min—
Mon 2 Nov— 21:03No data—
Sun 1 NovSantpoort Zuid 20:39+2 min+2 min
Sat 31 OctSantpoort Zuid 20:370 min—
Fri 30 Oct— 21:010 min—
Thu 29 Oct— 21:010 min—
Wed 28 Oct— 21:060 min—
Tue 27 Oct— 21:020 min—
Mon 26 Oct— 21:010 min—
Sun 25 OctHeiloo 21:05No data—
Sat 24 OctHeiloo 21:090 min—
Fri 23 Oct— 21:01+1 min—
Thu 22 Oct— 21:08No data—
Wed 21 Oct— 21:02No data—
Tue 20 Oct— 21:04No data—
Mon 19 Oct— 21:020 min—
Sun 18 OctHeiloo 21:040 min—
Sat 17 OctHeiloo 21:06No data—
Fri 16 OctAmsterdam Centraal 20:430 min—
Thu 15 Oct— 21:000 min—
Wed 14 Oct— 20:57No data—
Tue 13 Oct— 20:580 min—
Mon 12 Oct— 20:580 min—
Sun 11 OctAlkmaar Noord 21:190 min—
Sat 10 OctAlkmaar Noord 21:180 min+2 min
Fri 9 Oct— 21:18+7 min+8 min
Thu 8 Oct— 21:18+2 min+3 min
Wed 7 Oct— 21:110 min—