Train NS 4882 Alkmaar – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 00:04 from Alkmaar · Sun 8 Nov

Next departure 00:04 tomorrow · Alkmaar
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 4 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 12 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 Amsterdam Centraal, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:04on time on time
00:09≈ on time ≈ on time
00:15≈ on time ≈ on time
00:19 / 00:20≈ on time ≈ on time
00:24≈ on time ≈ on time
00:27 / 00:28≈ on time ≈ on time
00:33≈ on time ≈ on time
00:36≈ on time ≈ on time
00:39≈ on time ≈ on time
00:42≈ on time ≈ on time
00:46 / 00:47≈ on time ≈ on time
00:50≈ on time ≈ on time
00:55≈ on time ≈ on time
01:00≈ on time ≈ on time
01:05on 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
Fri 6 Nov— 00:270 min—
Thu 5 Nov— 00:28No data—
Wed 4 Nov— 00:280 min—
Mon 2 NovAmsterdam Sloterdijk 00:270 min—
Fri 30 Oct— 01:060 min—
Wed 28 Oct— 01:090 min—
Tue 27 Oct— 01:060 min—
Mon 26 Oct— 01:060 min—
Sun 25 OctAmsterdam Sloterdijk 01:14No data—
Sat 24 Oct— 01:07No data—
Fri 23 Oct— 01:06No data—
Wed 21 Oct— 01:060 min—
Mon 19 Oct— 01:060 min—
Sun 18 OctAmsterdam Sloterdijk 01:16+2 min+2 min
Sat 17 OctAmsterdam Sloterdijk 01:060 min+4 min
Fri 16 Oct— 01:060 min—
Thu 15 Oct— 01:060 min—
Wed 14 Oct— 01:070 min—
Tue 13 Oct— 01:060 min—
Sun 11 OctAmsterdam Sloterdijk 01:150 min—
Sat 10 Oct— 01:070 min—
Fri 9 Oct— 01:060 min—
Thu 8 Oct— 01:060 min—
Wed 7 Oct— 01:060 min—
Tue 6 Oct— 01:060 min—
Mon 5 OctBloemendaal 00:57No data—
Sun 4 OctDriehuis 00:48No data—
Sun 27 SeptAmsterdam Sloterdijk 01:18No data—
Sun 20 SeptAmsterdam Sloterdijk 01:14No data—
Sun 13 SeptAmsterdam Sloterdijk 01:14No data—