Train NS 4839 Amsterdam Centraal – Alkmaar

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

Running now · updated 13:25

Heading to Alkmaar 0 min

Estimated arrival at Alkmaar 13:56 · 0 km/h

  1. Amsterdam Centraal12:55
  2. Halfweg-Zwanenburg13:06
  3. Bloemendaal13:19
  4. Santpoort Noord13:24
  5. Beverwijk13:32
  6. Castricum13:45
  7. Alkmaar13:56

Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 17 runs arrived on time.

On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 14 full · 3 partial · 13 no data
On-time · 90 days
92%
23/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
+2min
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

  • Mon 5 Oct Max en route +8 min · last fix heading to Alkmaar Noord +7 min
  • Sat 7 Nov Max en route +6 min · last fix heading to Obdam +5 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 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 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, 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 10Today
12:55on time on time
13:01≈ on time ≈ on time
13:06≈ on time ≈ on time
13:10≈ on time ≈ on time
13:14 / 13:15≈ on time ≈ on time
13:19≈ on time ≈ on time
13:22≈ on time ≈ +1 min
13:24≈ on time ≈ +1 min
13:27≈ on time ≈ +1 min
13:32≈ on time ≈ +1 min
13:36≈ on time ≈ +1 min
13:40 / 13:41≈ on time ≈ +1 min
13:45≈ on time ≈ +1 min
13:51≈ on time ≈ +1 min
13: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 NovSantpoort Noord 13:24Partial coverage0 min—
Tue 10 NovHeiloo 14:08Partial coverage+2 min+2 min
Mon 9 NovHeiloo 14:07Partial coverage+2 min+2 min
Sun 8 NovObdam 14:300 min—
Sat 7 NovObdam 14:34+5 min+6 min
Fri 6 NovObdam 14:29No data—
Thu 5 NovObdam 14:29No data—
Wed 4 NovObdam 14:290 min—
Tue 3 NovObdam 14:29No data—
Mon 2 NovObdam 14:29No data—
Sun 1 NovSantpoort Zuid 13:38+1 min+1 min
Sat 31 OctSantpoort Zuid 13:38+1 min+1 min
Fri 30 OctObdam 14:290 min—
Thu 29 OctObdam 14:290 min—
Wed 28 OctObdam 14:290 min—
Tue 27 OctObdam 14:30No data—
Mon 26 OctObdam 14:29No data—
Sun 25 OctObdam 14:30No data—
Sat 24 OctObdam 14:290 min—
Fri 23 OctObdam 14:29No data—
Thu 22 OctObdam 14:29No data—
Wed 21 OctObdam 14:29No data—
Tue 20 OctObdam 14:290 min—
Mon 19 OctObdam 14:300 min—
Sun 18 OctObdam 14:300 min+1 min
Sat 17 OctObdam 14:29No data—
Fri 16 OctHeemskerk 13:50No data—
Thu 15 OctObdam 14:290 min—
Wed 14 OctObdam 14:30No data—
Tue 13 OctObdam 14:290 min—