Train NS 4823 Amsterdam Centraal – Alkmaar

Amsterdam Centraal 08:55 → Alkmaar 09:56 Daily 1 h 01 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heiloo at 10:04 0 min

  1. Amsterdam Centraal08:55
  2. Halfweg-Zwanenburg09:06
  3. Bloemendaal09:19
  4. Santpoort Noord09:24
  5. Beverwijk09:32
  6. Heiloo09:51
  7. Alkmaar09:56

Next service: tomorrow 08:55 from Amsterdam Centraal · Thu 12 Nov

Next departure 08:55 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 15 full · 3 partial · 12 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 22 full · 3 partial · 64 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 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

  • Sun 8 Nov Max en route +4 min · last fix heading to Obdam +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 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=3
  • 100% W n=6
  • 100% T n=3
  • 100% F n=1
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 25 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
08:55on time on time
09:01≈ on time ≈ on time
09:06≈ on time ≈ on time
09:10≈ on time ≈ on time
09:14 / 09:15≈ on time ≈ on time
09:19≈ on time ≈ on time
09:22≈ on time ≈ on time
09:24≈ on time ≈ on time
09:27≈ on time ≈ on time
09:32≈ on time ≈ on time
09:36≈ on time ≈ on time
09:40 / 09:41≈ on time ≈ on time
09:45≈ on time ≈ +1 min
09:51≈ on time ≈ +1 min
09:56on 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
Wed 11 NovHeiloo 10:04Partial coverage0 min—
Tue 10 NovHeiloo 10:04Partial coverage+1 min+2 min
Mon 9 NovHeiloo 10:04Partial coverage0 min—
Sun 8 NovObdam 10:33+4 min+4 min
Sat 7 NovObdam 10:290 min—
Fri 6 NovObdam 10:29No data—
Thu 5 NovObdam 10:29No data—
Wed 4 NovObdam 10:290 min—
Tue 3 NovObdam 10:29No data—
Mon 2 NovObdam 10:29No data—
Sun 1 NovSantpoort Zuid 09:38+1 min—
Sat 31 OctSantpoort Zuid 09:360 min+1 min
Fri 30 OctObdam 10:29No data—
Thu 29 OctHeiloo 11:500 min—
Wed 28 OctObdam 10:300 min—
Tue 27 OctObdam 10:290 min—
Mon 26 OctObdam 10:30No data—
Sun 25 OctObdam 10:29No data—
Sat 24 OctObdam 10:290 min—
Fri 23 OctObdam 10:29No data—
Thu 22 OctObdam 10:29No data—
Wed 21 OctObdam 10:300 min—
Tue 20 OctObdam 10:29No data—
Mon 19 OctObdam 10:330 min—
Sun 18 OctObdam 10:29+1 min—
Sat 17 OctObdam 10:30+1 min—
Fri 16 OctHeemskerk 09:50No data—
Thu 15 OctDriehuis 10:580 min—
Wed 14 OctObdam 10:290 min—
Tue 13 OctObdam 10:29No data—