Train NS 4841 Amsterdam Centraal – Alkmaar

Amsterdam Centraal 13:25 → Alkmaar 14:26 Daily 1 h 01 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heiloo at 14:34 0 min

  1. Amsterdam Centraal13:25
  2. Halfweg-Zwanenburg13:36
  3. Bloemendaal13:49
  4. Santpoort Noord13:54
  5. Beverwijk14:02
  6. Heiloo14:21
  7. Alkmaar14:26

Next service: tomorrow 13:25 from Amsterdam Centraal · Tue 10 Nov

Next departure 13:25 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 13 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 66 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

  • Sat 24 Oct Max en route +7 min · last fix heading to Obdam +7 min

Distribution · 90 days

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

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

Stops and timetable

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

Last 90 days, 23 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
13:25on time on time
13:31≈ on time ≈ on time
13:36≈ on time ≈ on time
13:40≈ on time ≈ on time
13:44 / 13:45≈ on time ≈ on time
13:49≈ on time ≈ on time
13:52≈ on time ≈ on time
13:54≈ on time ≈ on time
13:57≈ on time ≈ on time
14:02≈ on time ≈ on time
14:06≈ on time ≈ on time
14:10 / 14:11≈ on time ≈ on time
14:15≈ on time ≈ on time
14:21≈ on time ≈ on time
14:26on 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
Mon 9 NovHeiloo 14:34Partial coverage0 min—
Sun 8 NovObdam 14:590 min—
Sat 7 NovObdam 14:590 min—
Fri 6 NovObdam 14:59No data—
Thu 5 NovObdam 14:590 min—
Wed 4 NovObdam 14:590 min—
Tue 3 NovObdam 14:59No data—
Mon 2 NovObdam 14:590 min—
Sun 1 NovSantpoort Zuid 14:080 min—
Sat 31 OctSantpoort Zuid 14:060 min—
Fri 30 OctObdam 14:59No data—
Thu 29 OctObdam 14:590 min—
Wed 28 OctObdam 15:000 min—
Tue 27 OctObdam 15:000 min—
Mon 26 OctObdam 14:59No data—
Sun 25 OctObdam 14:59No data—
Sat 24 OctObdam 15:08+7 min+7 min
Fri 23 OctObdam 15:01No data—
Thu 22 OctObdam 15:00No data—
Wed 21 OctObdam 15:100 min—
Tue 20 OctObdam 15:04No data—
Mon 19 OctObdam 15:01No data—
Sun 18 OctObdam 14:590 min—
Sat 17 OctObdam 15:00No data—
Fri 16 OctHeemskerk 14:20No data—
Thu 15 OctObdam 14:590 min—
Wed 14 OctObdam 15:000 min—
Tue 13 OctObdam 15:00No data—
Mon 12 OctAlkmaar Noord 14:48No data—
Sun 11 OctAlkmaar Noord 14:480 min—