Train NS 4819 Amsterdam Centraal – Alkmaar

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

✓ Today’s run finished

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

  1. Amsterdam Centraal07:55
  2. Halfweg-Zwanenburg08:06
  3. Bloemendaal08:19
  4. Santpoort Noord08:24
  5. Beverwijk08:32
  6. Heiloo08:51
  7. Alkmaar08:56

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

Next departure 07:55 tomorrow · Amsterdam Centraal
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 26 full · 3 partial · 60 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: +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

  • Sat 24 Oct Max en route +7 min · last fix heading to Obdam +6 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Heiloo +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 80% S n=5
  • 100% S n=4

Stops and timetable

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

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