Train NS 4878 Alkmaar – Amsterdam Centraal

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

Running now · updated 00:02

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 00:05 · 72 km/h

  1. Alkmaar23:00
  2. Castricum23:10
  3. Beverwijk23:27
  4. Santpoort Noord23:36
  5. Bloemendaal23:42
  6. Halfweg-Zwanenburg23:55
  7. Amsterdam Centraal00:05

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 6 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 30 full · 3 partial · 20 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

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 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=4
  • 100% F n=5
  • 100% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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 10Today
23:00on time on time
23:05≈ on time ≈ on time
23:10≈ on time ≈ on time
23:14 / 23:20≈ on time ≈ on time
23:24≈ on time ≈ on time
23:27 / 23:28≈ on time ≈ on time
23:33≈ on time ≈ on time
23:36≈ on time ≈ on time
23:39≈ on time ≈ on time
23:42≈ on time ≈ on time
23:46 / 23:47≈ on time ≈ on time
23:50≈ on time ≈ on time
23:55≈ on time ≈ on time
00:00≈ on time ≈ on time
00: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
Sun 15 NovAmsterdam Sloterdijk 23:59Partial coverage0 min+2 min
Sat 14 NovAlkmaar 23:28Partial coverage0 min—
Fri 13 Nov— 00:04+2 min+2 min
Thu 12 Nov— 00:080 min+3 min
Wed 11 Nov— 00:040 min—
Tue 10 Nov— 00:040 min—
Mon 9 Nov— 00:040 min—
Sun 8 NovAmsterdam Sloterdijk 00:140 min—
Sat 7 NovUitgeest 23:390 min—
Fri 6 Nov— 23:240 min—
Thu 5 Nov— 23:280 min—
Wed 4 Nov— 23:290 min+2 min
Mon 2 Nov— 23:270 min—
Sun 1 NovAmsterdam Sloterdijk 00:140 min—
Sat 31 Oct— 00:07No data—
Fri 30 Oct— 00:06No data—
Thu 29 Oct— 00:060 min—
Wed 28 Oct— 00:06No data—
Tue 27 Oct— 00:060 min—
Mon 26 Oct— 00:060 min—
Sun 25 OctAmsterdam Sloterdijk 00:14No data—
Sat 24 Oct— 00:07No data—
Fri 23 Oct— 00:09+2 min+2 min
Thu 22 Oct— 00:06No data—
Wed 21 Oct— 00:060 min—
Tue 20 Oct— 00:060 min—
Mon 19 Oct— 00:070 min—
Sun 18 OctAmsterdam Sloterdijk 00:14Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 00:15No data—
Fri 16 Oct— 00:060 min—