Train NS 4881 Beverwijk – Alkmaar

Beverwijk 00:02 → Alkmaar 00:30 Mon, Tue, Wed, Thu, Sat, Sun 0 h 28 min · 6 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Tuesday 3 November +4 min

Next service: Saturday 00:02 from Beverwijk · Sat 7 Nov

Next departure 00:02 Saturday · Beverwijk
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 25 full · 1 partial · 1 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Tue 3 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +3 min · last fix heading to — +3 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 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 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 (6 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.

StopSched.Usually 9 days in 10
00:02on time on time
00:06≈ on time ≈ on time
00:10 / 00:15≈ on time ≈ on time
00:20≈ on time ≈ on time
00:25≈ on time ≈ on time
00:30on time on time

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
Tue 3 Nov— 00:33+4 min+4 min
Sun 1 NovSantpoort Zuid 00:04Partial coverage0 min—
Sat 31 Oct— 23:59No data—
Fri 30 Oct— 00:550 min—
Thu 29 Oct— 00:310 min—
Wed 28 Oct— 00:310 min—
Tue 27 Oct— 00:310 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctHeiloo 00:400 min—
Sat 24 Oct— 01:000 min—
Fri 23 Oct— 01:140 min—
Thu 22 Oct— 00:180 min—
Wed 21 Oct— 00:320 min—
Tue 20 Oct— 00:310 min—
Mon 19 Oct— 00:340 min—
Sun 18 OctHeiloo 00:410 min—
Sat 17 OctObdam 00:590 min—
Fri 16 Oct— 00:15+3 min+3 min
Thu 15 Oct— 00:350 min—
Wed 14 Oct— 00:270 min—
Tue 13 Oct— 00:270 min—
Mon 12 Oct— 00:270 min—
Sun 11 OctHeiloo 00:390 min—
Sat 10 Oct— 00:410 min—
Fri 9 Oct— 00:410 min—
Thu 8 Oct— 00:310 min—
Wed 7 Oct— 00:310 min—
Tue 6 Oct— 00:480 min+13 min
Mon 5 OctHeemskerk 00:310 min—
Sun 4 OctHeemskerk 00:20No data—