Train NS 4822 Alkmaar – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 09:00 from Alkmaar · Mon 16 Nov

Next departure 09:00 today · Alkmaar
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 60 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: +1 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

Worst days

  • Sat 7 Nov Max en route +11 min · last fix heading to Amsterdam Sloterdijk +11 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 83% 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, 28 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
09:00on time on time
09:05≈ on time ≈ on time
09:10≈ on time ≈ on time
09:14 / 09:20≈ on time ≈ on time
09:24≈ on time ≈ +1 min
09:27 / 09:28≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09:36≈ on time ≈ +1 min
09:39≈ on time ≈ +1 min
09:42≈ on time ≈ +1 min
09:46 / 09:47≈ on time ≈ +1 min
09:50≈ on time ≈ +1 min
09:55≈ on time ≈ +2 min
10:00≈ on time ≈ +2 min
10:05on 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
Sun 15 NovAmsterdam Sloterdijk 10:14Partial coverage0 min—
Sat 14 NovAmsterdam Sloterdijk 10:170 min—
Fri 13 NovAmsterdam Sloterdijk 10:19+5 min+5 min
Thu 12 NovAmsterdam Sloterdijk 10:140 min—
Wed 11 NovAmsterdam Sloterdijk 10:140 min—
Tue 10 NovAmsterdam Sloterdijk 10:14+1 min+2 min
Mon 9 NovAmsterdam Sloterdijk 10:140 min+1 min
Sun 8 NovAmsterdam Sloterdijk 10:140 min—
Sat 7 NovAmsterdam Sloterdijk 10:29+11 min+11 min
Fri 6 NovHeemskerk 09:38No data—
Thu 5 NovHeemskerk 09:37No data—
Wed 4 NovHeemskerk 09:38+1 min—
Tue 3 NovHeemskerk 09:37No data—
Mon 2 NovHeemskerk 09:37No data—
Sun 1 NovAmsterdam Sloterdijk 10:17+1 min+2 min
Sat 31 OctAmsterdam Sloterdijk 10:140 min—
Fri 30 OctAmsterdam Sloterdijk 10:150 min—
Thu 29 OctAmsterdam Sloterdijk 10:200 min—
Wed 28 OctAmsterdam Sloterdijk 10:150 min—
Tue 27 OctAmsterdam Sloterdijk 10:140 min—
Mon 26 OctAmsterdam Sloterdijk 10:14No data—
Sun 25 OctAmsterdam Sloterdijk 10:14No data—
Sat 24 OctAmsterdam Sloterdijk 10:140 min—
Fri 23 OctAmsterdam Sloterdijk 10:140 min—
Thu 22 OctAmsterdam Sloterdijk 10:140 min—
Wed 21 OctAmsterdam Sloterdijk 10:14No data—
Tue 20 OctAmsterdam Sloterdijk 10:140 min—
Mon 19 OctAmsterdam Sloterdijk 10:14No data—
Sun 18 OctAmsterdam Sloterdijk 10:140 min—
Sat 17 OctAmsterdam Sloterdijk 10:140 min—