Train NS 4867 Amsterdam Centraal → Alkmaar

Amsterdam Centraal 19:55 → Alkmaar 21:00 Daily 1 h 05 min · 15 stops NS (Nederlandse Spoorwegen)

NS 4867 Amsterdam Centraal–Alkmaar: final delay under 3 min on 24 of its 25 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:15 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +2 min

Next service: today 19:55 from Amsterdam Centraal · Sun 22 Nov

Next departure 19:55 today · Amsterdam Centraal
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 24 full · 1 partial · 3 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 38 full · 1 partial · 20 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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +7 min
  • Fri 13 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
19:55on time on time
20:01≈ on time ≈ on time
20:06≈ on time ≈ on time
20:10≈ on time ≈ on time
20:14 / 20:15≈ on time ≈ +1 min
20:19≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:24≈ on time ≈ +1 min
20:27≈ on time ≈ +1 min
20:32≈ on time ≈ +1 min
20:36≈ on time ≈ +1 min
20:40 / 20:45≈ on time ≈ +1 min
20:50≈ on time ≈ +2 min
20:55≈ on time ≈ +2 min
21:00on time +2 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
Sat 21 NovHeiloo 21:09Partial coverage+2 min+2 min
Fri 20 Nov— 20:590 min—
Thu 19 Nov— 20:090 min+3 min
Wed 18 Nov— 20:59+1 min—
Tue 17 Nov— 20:590 min—
Mon 16 Nov— 21:030 min—
Sun 15 NovHeiloo 21:04+2 min+2 min
Sat 14 NovHeiloo 21:090 min—
Fri 13 Nov— 21:04+3 min+3 min
Thu 12 Nov— 20:040 min—
Wed 11 Nov— 20:59+2 min+2 min
Tue 10 Nov— 20:59+2 min+2 min
Mon 9 Nov— 21:02+1 min+1 min
Sun 8 NovHeiloo 21:040 min+2 min
Sat 7 NovHeiloo 21:040 min—
Fri 6 Nov— 21:04+1 min+1 min
Thu 5 Nov— 21:00No data—
Wed 4 Nov— 21:02+1 min—
Mon 2 Nov— 21:03No data—
Sun 1 NovSantpoort Zuid 20:39+2 min+2 min
Sat 31 OctSantpoort Zuid 20:370 min—
Fri 30 Oct— 21:010 min—
Thu 29 Oct— 21:010 min—
Wed 28 Oct— 21:060 min—
Tue 27 Oct— 21:020 min—
Mon 26 Oct— 21:010 min—
Sun 25 OctHeiloo 21:05No data—
Sat 24 OctHeiloo 21:090 min—
Fri 23 Oct— 21:01+1 min—
Thu 22 Oct— 21:08No data—