Train NS 4826 Alkmaar – Amsterdam Centraal

Alkmaar 10:04 → Amsterdam Centraal 11:06 Daily 1 h 02 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Halfweg-Zwanenburg at 11:27 +10 min

  1. Alkmaar10:04
  2. Castricum10:14
  3. Beverwijk10:27
  4. Santpoort Noord10:37
  5. Halfweg-Zwanenburg10:56
  6. Amsterdam Sloterdijk11:01
  7. Amsterdam Centraal11:06

Next service: tomorrow 10:04 from Alkmaar · Thu 12 Nov

Next departure 10:04 tomorrow · Alkmaar
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 24 full · 3 partial · 62 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

Worst days

  • Wed 11 Nov Max en route +10 min · last fix heading to Halfweg-Zwanenburg +10 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
10:04on time on time
10:09≈ on time ≈ on time
10:14≈ on time ≈ on time
10:19≈ on time ≈ on time
10:24≈ on time ≈ on time
10:27 / 10:30≈ on time ≈ on time
10:34≈ on time ≈ on time
10:37≈ on time ≈ on time
10:40≈ on time ≈ on time
10:43≈ on time ≈ on time
10:47 / 10:48≈ on time ≈ on time
10:51≈ on time ≈ on time
10:56≈ on time ≈ on time
11:01≈ on time ≈ on time
11:06on 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
Wed 11 NovHalfweg-Zwanenburg 11:27Partial coverage+10 min+10 min
Tue 10 NovAmsterdam Sloterdijk 11:14Partial coverage0 min—
Mon 9 NovAmsterdam Sloterdijk 11:14Partial coverage0 min—
Sun 8 NovAmsterdam Sloterdijk 11:140 min—
Sat 7 NovBloemendaal 11:280 min—
Fri 6 NovHeemskerk 10:38No data—
Thu 5 NovHeemskerk 10:38No data—
Wed 4 NovHeemskerk 10:370 min—
Tue 3 NovHeemskerk 10:38No data—
Mon 2 NovHeemskerk 10:37No data—
Sun 1 NovAmsterdam Sloterdijk 11:150 min—
Sat 31 OctAmsterdam Sloterdijk 11:16+1 min+1 min
Fri 30 OctAmsterdam Sloterdijk 11:150 min—
Thu 29 OctAmsterdam Sloterdijk 11:170 min—
Wed 28 OctAmsterdam Sloterdijk 11:150 min—
Tue 27 OctAmsterdam Sloterdijk 11:150 min—
Mon 26 OctAmsterdam Sloterdijk 11:150 min—
Sun 25 OctAmsterdam Sloterdijk 11:15No data—
Sat 24 OctAmsterdam Sloterdijk 11:16+1 min+2 min
Fri 23 OctAmsterdam Sloterdijk 11:150 min—
Thu 22 OctAmsterdam Sloterdijk 11:150 min—
Wed 21 OctAmsterdam Sloterdijk 11:17No data—
Tue 20 OctAmsterdam Sloterdijk 11:190 min—
Mon 19 OctAmsterdam Sloterdijk 11:160 min—
Sun 18 OctAmsterdam Sloterdijk 11:150 min—
Sat 17 OctAmsterdam Sloterdijk 11:150 min—
Fri 16 OctAmsterdam Sloterdijk 11:17No data—
Thu 15 OctAmsterdam Sloterdijk 11:17No data—
Wed 14 OctAmsterdam Sloterdijk 11:160 min—
Tue 13 OctAmsterdam Sloterdijk 11:160 min—