Train NS 4810 Alkmaar – Beverwijk

Alkmaar 06:00 → Beverwijk 06:26 Mon, Tue, Wed, Thu, Fri, Sat 0 h 26 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heemskerk at 06:37 0 min

  1. Alkmaar06:00
  2. Heiloo06:05
  3. Castricum06:10
  4. Uitgeest06:14
  5. Heemskerk06:22
  6. Beverwijk06:26

Next service: tomorrow 06:00 from Alkmaar · Fri 6 Nov

Next departure 06:00 tomorrow · Alkmaar
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 25 full · 1 partial · 50 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

Worst days

  • Thu 29 Oct Max en route +7 min · last fix heading to Amsterdam Sloterdijk +7 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 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 80% T n=5
  • 100% F n=4
  • 100% S n=4
  • — S n=0

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
06:00on time on time
06:05≈ on time ≈ on time
06:10≈ on time ≈ on time
06:14 / 06:18≈ on time ≈ on time
06:22≈ on time ≈ +1 min
06: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 NovHeemskerk 06:37Partial coverage0 min—
Wed 4 NovHeemskerk 06:340 min—
Tue 3 NovHeemskerk 06:370 min—
Mon 2 NovHeemskerk 06:37No data—
Sat 31 OctAmsterdam Sloterdijk 07:140 min—
Fri 30 OctAmsterdam Sloterdijk 07:140 min—
Thu 29 OctAmsterdam Sloterdijk 07:21+7 min+7 min
Wed 28 OctAmsterdam Sloterdijk 07:140 min—
Tue 27 OctAmsterdam Sloterdijk 07:140 min—
Mon 26 OctAmsterdam Sloterdijk 07:140 min—
Sat 24 OctAmsterdam Sloterdijk 07:140 min—
Fri 23 OctAmsterdam Sloterdijk 07:16+1 min+2 min
Thu 22 OctAmsterdam Sloterdijk 07:15+1 min—
Wed 21 OctAmsterdam Sloterdijk 07:140 min—
Tue 20 OctAmsterdam Sloterdijk 07:140 min—
Mon 19 OctAmsterdam Sloterdijk 07:140 min—
Sat 17 OctAmsterdam Sloterdijk 07:140 min—
Fri 16 OctAmsterdam Sloterdijk 07:140 min—
Thu 15 OctAmsterdam Sloterdijk 07:140 min—
Wed 14 OctAmsterdam Sloterdijk 07:140 min—
Tue 13 OctAmsterdam Sloterdijk 07:140 min—
Mon 12 OctAmsterdam Sloterdijk 07:140 min—
Sat 10 OctAmsterdam Sloterdijk 07:140 min—
Fri 9 OctAmsterdam Sloterdijk 07:140 min—
Thu 8 OctAmsterdam Sloterdijk 07:15+1 min—
Wed 7 OctAmsterdam Sloterdijk 07:140 min—
Tue 6 OctAmsterdam Sloterdijk 07:140 min—
Mon 5 OctAmsterdam Sloterdijk 07:15No data—
Sat 3 OctBloemendaal 06:59No data—
Fri 2 OctAmsterdam Sloterdijk 07:14No data—