Train NS 4881 Amsterdam Centraal → Alkmaar

Amsterdam Centraal 23:25 → Alkmaar 00:30 Daily 1 h 05 min · 15 stops NS (Nederlandse Spoorwegen)

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

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 23:25 from Amsterdam Centraal · Sun 22 Nov

Next departure 23:25 today · Amsterdam Centraal
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 1 no data
On-time · 90 days
95%
41/43 runs under 3 min
RT coverage: 42 full · 1 partial · 10 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

Worst days

  • Tue 3 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 43 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
23:25on time on time
23:31≈ on time ≈ on time
23:36≈ on time ≈ on time
23:40≈ on time ≈ on time
23:44 / 23:45≈ on time ≈ on time
23:49≈ on time ≈ on time
23:52≈ on time ≈ on time
23:54≈ on time ≈ on time
23:57≈ on time ≈ on time
00:02≈ on time ≈ on time
00:06≈ on time ≈ on time
00:10 / 00:15≈ on time ≈ on time
00:20≈ on time ≈ on time
00:25≈ on time ≈ on time
00:30on 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
Sat 21 Nov— 00:590 min—
Fri 20 Nov— 00:580 min—
Thu 19 Nov— 00:290 min—
Wed 18 Nov— 00:34+1 min+1 min
Tue 17 Nov— 00:300 min—
Mon 16 NovAmsterdam Centraal 00:290 min—
Sun 15 NovHeiloo 00:39Partial coverage0 min—
Sat 14 Nov— 23:440 min—
Fri 13 Nov— 00:340 min—
Thu 12 Nov— 00:340 min—
Wed 11 Nov— 00:290 min—
Tue 10 Nov— 00:340 min—
Mon 9 Nov— 00:340 min—
Sun 8 NovHeiloo 00:390 min—
Sat 7 Nov— 23:440 min—
Tue 3 Nov— 00:33+4 min+4 min
Sun 1 NovSantpoort Zuid 00:040 min—
Sat 31 Oct— 23:59No data—
Fri 30 Oct— 00:550 min—
Thu 29 Oct— 00:310 min—
Wed 28 Oct— 00:310 min—
Tue 27 Oct— 00:310 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctHeiloo 00:400 min—
Sat 24 Oct— 01:000 min—
Fri 23 Oct— 01:140 min—
Thu 22 Oct— 00:180 min—
Wed 21 Oct— 00:320 min—
Tue 20 Oct— 00:310 min—
Mon 19 Oct— 00:340 min—