Train NS 4885 Amsterdam Centraal – Alkmaar

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

✓ Today’s run finished

Today, last fix heading to — at 01:29 0 min

  1. Amsterdam Centraal00:25
  2. Halfweg-Zwanenburg00:36
  3. Bloemendaal00:49
  4. Santpoort Noord00:54
  5. Beverwijk01:02
  6. Castricum01:15
  7. Alkmaar01:26

Next service: tomorrow 00:25 from Amsterdam Centraal · Fri 13 Nov

Next departure 00:25 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 6 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 35 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
00:25on time on time
00:31≈ on time ≈ on time
00:36≈ on time ≈ on time
00:40≈ on time ≈ on time
00:44 / 00:45≈ on time ≈ on time
00:49≈ on time ≈ on time
00:52≈ on time ≈ on time
00:54≈ on time ≈ on time
00:57≈ on time ≈ on time
01:02≈ on time ≈ on time
01:06≈ on time ≈ on time
01:10 / 01:11≈ on time ≈ on time
01:15≈ on time ≈ on time
01:21≈ on time ≈ on time
01: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
Thu 12 Nov— 01:290 min—
Wed 11 Nov— 00:440 min—
Tue 10 Nov— 00:440 min—
Mon 9 NovHaarlem Spaarnwoude 00:590 min—
Sun 8 Nov— 01:280 min—
Sat 7 Nov— 01:270 min—
Fri 6 Nov— 01:390 min—
Thu 5 Nov— 01:280 min—
Mon 2 NovHaarlem Spaarnwoude 00:540 min—
Sun 1 Nov— 00:580 min—
Fri 30 Oct— 01:270 min—
Thu 29 Oct— 01:270 min—
Wed 28 Oct— 00:450 min—
Tue 27 Oct— 00:450 min—
Mon 26 OctHaarlem Spaarnwoude 00:570 min—
Sun 25 Oct— 01:270 min—
Sat 24 Oct— 01:320 min—
Fri 23 Oct— 01:270 min—
Thu 22 Oct— 01:280 min—
Wed 21 Oct— 00:470 min—
Tue 20 Oct— 00:450 min—
Mon 19 OctHaarlem Spaarnwoude 00:550 min—
Sun 18 OctHeemskerk 01:200 min—
Sat 17 Oct— 01:110 min—
Fri 16 Oct— 01:110 min—
Thu 15 Oct— 01:330 min—
Wed 14 Oct— 00:460 min—
Tue 13 Oct— 00:450 min—
Mon 12 OctHaarlem Spaarnwoude 00:540 min—
Sun 11 Oct— 01:280 min—