Train NS 4838 Alkmaar – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 13:04 from Alkmaar · Tue 10 Nov

Next departure 13:04 today · Alkmaar
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
96%
27/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
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 7 Oct Max en route +10 min · last fix heading to Amsterdam Sloterdijk +10 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 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 75% W n=4
  • 100% T n=4
  • 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, 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
13:04on time on time
13:09≈ on time ≈ on time
13:14≈ on time ≈ on time
13:19≈ on time ≈ on time
13:24≈ on time ≈ on time
13:27 / 13:30≈ on time ≈ on time
13:34≈ on time ≈ on time
13:37≈ on time ≈ on time
13:40≈ on time ≈ on time
13:43≈ on time ≈ on time
13:47 / 13:48≈ on time ≈ on time
13:51≈ on time ≈ on time
13:56≈ on time ≈ on time
14:01≈ on time ≈ on time
14: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
Mon 9 NovAmsterdam Sloterdijk 14:14Partial coverage0 min—
Sun 8 NovAmsterdam Sloterdijk 14:140 min—
Sat 7 NovAmsterdam Sloterdijk 14:280 min—
Fri 6 NovHeemskerk 13:38No data—
Thu 5 NovHeemskerk 13:370 min—
Wed 4 NovHeemskerk 13:370 min—
Tue 3 NovHeemskerk 13:380 min—
Mon 2 NovHeemskerk 13:37No data—
Sun 1 NovAmsterdam Sloterdijk 14:160 min—
Sat 31 OctAmsterdam Sloterdijk 14:150 min—
Fri 30 OctAmsterdam Sloterdijk 14:160 min—
Thu 29 OctAmsterdam Sloterdijk 14:150 min—
Wed 28 OctAmsterdam Sloterdijk 14:150 min—
Tue 27 OctAmsterdam Sloterdijk 14:150 min—
Mon 26 OctAmsterdam Sloterdijk 14:150 min—
Sun 25 OctAmsterdam Sloterdijk 14:16No data—
Sat 24 OctAmsterdam Sloterdijk 14:150 min—
Fri 23 OctAmsterdam Sloterdijk 14:150 min—
Thu 22 OctAmsterdam Sloterdijk 14:150 min—
Wed 21 OctAmsterdam Sloterdijk 14:150 min—
Tue 20 OctAmsterdam Sloterdijk 14:160 min—
Mon 19 OctAmsterdam Sloterdijk 14:170 min—
Sun 18 OctAmsterdam Sloterdijk 14:160 min—
Sat 17 OctAmsterdam Sloterdijk 14:18No data—
Fri 16 OctAmsterdam Sloterdijk 14:15No data—
Thu 15 OctAmsterdam Sloterdijk 14:15No data—
Wed 14 OctAmsterdam Sloterdijk 14:15No data—
Tue 13 OctAmsterdam Sloterdijk 14:150 min—
Mon 12 OctAmsterdam Sloterdijk 14:16No data—
Sun 11 OctAmsterdam Sloterdijk 14:150 min—