Train NS 4874 Alkmaar – Beverwijk

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:00 from Alkmaar · Fri 6 Nov

Next departure 22:00 today · Alkmaar
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%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 26 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 Beverwijk, 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

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

  • Early 0% · 0
  • On time 100% · 23
  • 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=3
  • 100% W n=3
  • 100% T n=5
  • 100% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 23 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
22:00on time on time
22:05≈ on time ≈ on time
22:10≈ on time ≈ +1 min
22:14 / 22:19≈ on time ≈ +1 min
22:23≈ on time ≈ +1 min
22:26on 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:280 min—
Wed 4 Nov— 22:280 min—
Tue 3 Nov— 22:280 min—
Mon 2 Nov— 22:280 min—
Sun 1 NovAmsterdam Sloterdijk 23:14+1 min+2 min
Sat 31 OctAmsterdam Sloterdijk 23:140 min—
Fri 30 Oct— 23:07No data—
Thu 29 Oct— 23:080 min+1 min
Wed 28 Oct— 23:07No data—
Tue 27 Oct— 23:09No data—
Mon 26 Oct— 23:07No data—
Sun 25 OctAmsterdam Sloterdijk 23:16No data—
Sat 24 OctSantpoort Zuid 23:07No data—
Fri 23 Oct— 23:080 min—
Thu 22 Oct— 23:080 min—
Wed 21 Oct— 23:07No data—
Tue 20 Oct— 23:07No data—
Mon 19 Oct— 22:020 min—
Sun 18 OctAmsterdam Sloterdijk 23:150 min—
Sat 17 OctAmsterdam Sloterdijk 23:16No data—
Fri 16 Oct— 23:070 min—
Thu 15 Oct— 23:100 min—
Wed 14 Oct— 23:11+1 min+1 min
Tue 13 Oct— 23:080 min—
Mon 12 Oct— 23:12+2 min+2 min
Sun 11 OctAmsterdam Sloterdijk 23:150 min—
Sat 10 OctHeiloo 23:07+1 min—
Fri 9 Oct— 23:070 min—
Thu 8 Oct— 23:080 min—
Wed 7 Oct— 23:08+2 min+2 min