Train NS 4836 Alkmaar – Amsterdam Centraal

Alkmaar 12:34 → Amsterdam Centraal 13:35 Daily 1 h 01 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 12:34 from Alkmaar · Wed 11 Nov

Next departure 12:34 today · Alkmaar
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 17 full · 2 partial · 10 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 24 full · 2 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

  • Mon 5 Oct Max en route +6 min · last fix heading to Amsterdam Sloterdijk +6 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
12:34on time on time
12:39≈ on time ≈ on time
12:44≈ on time ≈ on time
12:49≈ on time ≈ on time
12:54≈ on time ≈ on time
12:57 / 12:58≈ on time ≈ on time
13:03≈ on time ≈ on time
13:05≈ on time ≈ on time
13:08≈ on time ≈ on time
13:11≈ on time ≈ on time
13:15 / 13:17≈ on time ≈ on time
13:20≈ on time ≈ on time
13:25≈ on time ≈ on time
13:30≈ on time ≈ on time
13:35on 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
Tue 10 NovAmsterdam Sloterdijk 13:44Partial coverage0 min+1 min
Mon 9 NovAmsterdam Sloterdijk 13:44Partial coverage0 min—
Sun 8 NovAmsterdam Sloterdijk 13:440 min—
Sat 7 NovAmsterdam Sloterdijk 13:440 min—
Fri 6 NovHeemskerk 13:09No data—
Thu 5 NovHeemskerk 13:070 min—
Wed 4 NovHeemskerk 13:070 min—
Tue 3 NovHeemskerk 13:07No data—
Mon 2 NovHeemskerk 13:07No data—
Sun 1 NovAmsterdam Sloterdijk 13:450 min—
Sat 31 OctAmsterdam Sloterdijk 13:440 min—
Fri 30 OctAmsterdam Sloterdijk 13:440 min—
Thu 29 OctAmsterdam Sloterdijk 13:450 min—
Wed 28 OctAmsterdam Sloterdijk 13:440 min—
Tue 27 OctAmsterdam Sloterdijk 13:510 min—
Mon 26 OctAmsterdam Sloterdijk 13:450 min—
Sun 25 OctAmsterdam Sloterdijk 13:44No data—
Sat 24 OctAmsterdam Sloterdijk 13:460 min+1 min
Fri 23 OctAmsterdam Sloterdijk 13:440 min—
Thu 22 OctAmsterdam Sloterdijk 13:44No data—
Wed 21 OctAmsterdam Sloterdijk 13:440 min—
Tue 20 OctAmsterdam Sloterdijk 13:44No data—
Mon 19 OctAmsterdam Sloterdijk 13:47No data—
Sun 18 OctAmsterdam Sloterdijk 13:440 min—
Sat 17 OctAmsterdam Sloterdijk 13:44No data—
Fri 16 OctAmsterdam Sloterdijk 13:44No data—
Thu 15 OctAmsterdam Sloterdijk 13:45No data—
Wed 14 OctAmsterdam Sloterdijk 13:460 min—
Tue 13 OctAmsterdam Sloterdijk 13:450 min—
Mon 12 OctAmsterdam Sloterdijk 13:47No data—