Train NS 4815 Amsterdam Centraal – Alkmaar

Amsterdam Centraal 06:55 → Alkmaar 07:56 Mon, Tue, Wed, Thu, Fri, Sat 1 h 01 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heiloo at 08:07 +2 min

  1. Amsterdam Centraal06:55
  2. Halfweg-Zwanenburg07:06
  3. Bloemendaal07:19
  4. Santpoort Noord07:24
  5. Beverwijk07:32
  6. Heiloo07:51
  7. Alkmaar07:56

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

Next departure 06:55 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 2 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 27 full · 3 partial · 46 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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