Train NS 4879 Beverwijk – Alkmaar

Beverwijk 23:32 → Alkmaar 00: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 23:32 from Beverwijk · Sat 7 Nov

Next departure 23:32 today · Beverwijk
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 4 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 26 full · 0 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Mon 19 Oct Max en route +14 min · last fix heading to — +14 min
  • Mon 12 Oct Max en route +12 min · last fix heading to — +12 min
  • Fri 16 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 50% M n=4
  • 100% T n=4
  • 100% W n=5
  • 100% T n=2
  • 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, 26 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
23:32on time on time
23:36≈ on time ≈ +1 min
23:40 / 23:45≈ on time ≈ +1 min
23:50≈ on time ≈ +2 min
23:55≈ on time ≈ +3 min
00:00on time +4 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— 23:59+1 min—
Thu 5 Nov— 00:24No data—
Wed 4 Nov— 00:250 min—
Sun 1 NovSantpoort Zuid 23:370 min—
Sat 31 OctSantpoort Zuid 23:36No data—
Fri 30 Oct— 00:010 min—
Wed 28 Oct— 00:400 min—
Tue 27 Oct— 00:270 min—
Mon 26 Oct— 00:290 min—
Sun 25 OctObdam 00:30No data—
Sat 24 Oct— 00:010 min—
Fri 23 Oct— 00:02+1 min—
Thu 22 Oct— 00:17No data—
Wed 21 Oct— 00:260 min—
Tue 20 Oct— 00:250 min—
Mon 19 Oct— 00:54+14 min+14 min
Sun 18 OctObdam 00:290 min—
Sat 17 OctHeiloo 00:070 min—
Fri 16 Oct— 23:48+6 min+6 min
Thu 15 Oct— 00:250 min—
Wed 14 Oct— 00:250 min—
Tue 13 Oct— 00:310 min—
Mon 12 Oct— 00:48+12 min+12 min
Sun 11 OctAlkmaar Noord 00:180 min—
Sat 10 Oct— 00:140 min—
Fri 9 Oct— 00:120 min+1 min
Thu 8 Oct— 00:12+1 min—
Wed 7 Oct— 00:110 min—
Tue 6 Oct— 00:110 min—
Mon 5 OctHeemskerk 00:120 min—