Train NS 4863 Beverwijk – Alkmaar

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 19:32 from Beverwijk · Fri 6 Nov

Next departure 19:32 today · Beverwijk
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 11 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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 +9 min · last fix heading to — +8 min
  • Wed 7 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 67% W n=3
  • 100% T n=4
  • 50% F n=2
  • 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, 19 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
19:32on time on time
19:36≈ on time ≈ on time
19:40 / 19:45≈ on time ≈ +1 min
19:50≈ on time ≈ +2 min
19:55≈ on time ≈ +3 min
20:00on time +3 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— 19:590 min—
Wed 4 Nov— 19:590 min—
Mon 2 Nov— 19:59No data—
Sun 1 NovSantpoort Zuid 19:370 min—
Sat 31 OctSantpoort Zuid 19:360 min—
Thu 29 Oct— 19:430 min—
Wed 28 Oct— 20:010 min—
Tue 27 Oct— 20:02No data—
Mon 26 OctCastricum 20:010 min—
Sun 25 OctHeiloo 20:04No data—
Sat 24 OctHeiloo 20:060 min—
Fri 23 OctDriehuis 20:020 min—
Thu 22 Oct— 20:02No data—
Wed 21 Oct— 20:02No data—
Tue 20 Oct— 20:01No data—
Mon 19 Oct— 20:04No data—
Sun 18 OctHeiloo 20:07+3 min+3 min
Sat 17 OctHeiloo 20:05No data—
Fri 16 OctHeemskerk 19:49No data—
Thu 15 Oct— 19:590 min—
Wed 14 OctCastricum 19:59No data—
Tue 13 Oct— 19:59No data—
Mon 12 Oct— 19:580 min—
Sun 11 OctAlkmaar Noord 20:19+1 min—
Sat 10 OctAlkmaar Noord 20:180 min—
Fri 9 Oct— 20:18+8 min+9 min
Thu 8 Oct— 20:160 min—
Wed 7 Oct— 20:18+5 min+5 min
Tue 6 Oct— 20:15+1 min—
Mon 5 Oct— 20:110 min—