Train NS 4875 Beverwijk – Alkmaar

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

Running now · updated 22:46

Heading to Alkmaar 0 min

Estimated arrival at Alkmaar 23:00 · 96 km/h

  1. Beverwijk22:32
  2. Heemskerk22:36
  3. Uitgeest22:40
  4. Castricum22:50
  5. Heiloo22:55
  6. Alkmaar23:00

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 20 runs arrived on time.

On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 100% F n=3
  • 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, 22 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 10Today
22:32on time on time
22:36≈ on time ≈ on time
22:40 / 22:45≈ on time ≈ on time
22:50≈ on time ≈ +1 min
22:55≈ on time ≈ +1 min
23:00on 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

DateLast stopFinalMax
Thu 5 Nov— 22:440 min—
Wed 4 Nov— 23:04+1 min+1 min
Tue 3 Nov— 23:00No data—
Mon 2 Nov— 22:590 min—
Sun 1 NovSantpoort Zuid 22:370 min+1 min
Sat 31 OctSantpoort Zuid 22:360 min—
Thu 29 Oct— 21:570 min—
Wed 28 Oct— 23:010 min—
Tue 27 Oct— 23:02No data—
Mon 26 Oct— 23:01No data—
Sun 25 OctHeiloo 23:09No data—
Sat 24 OctHeemskerk 23:010 min—
Fri 23 Oct— 23:010 min—
Thu 22 Oct— 23:020 min—
Wed 21 Oct— 23:01No data—
Tue 20 Oct— 23:02No data—
Mon 19 Oct— 23:020 min—
Sun 18 OctHeiloo 23:10+1 min—
Sat 17 OctHeiloo 23:05No data—
Fri 16 Oct— 22:420 min—
Thu 15 Oct— 22:59No data—
Wed 14 Oct— 22:57No data—
Tue 13 Oct— 23:000 min—
Mon 12 Oct— 22:58+1 min—
Sun 11 OctAlkmaar Noord 23:190 min—
Sat 10 OctAmsterdam Sloterdijk 23:12+1 min+1 min
Fri 9 Oct— 23:130 min+1 min
Thu 8 Oct— 23:140 min—
Wed 7 Oct— 23:11+1 min—
Tue 6 Oct— 23:14+1 min+1 min