Train NS 4097 Alkmaar → Amsterdam Centraal

Alkmaar 00:31 → Amsterdam Centraal 01:17 Mon, Tue, Wed, Thu, Sun 0 h 46 min · 11 stops NS (Nederlandse Spoorwegen)

NS 4097 Alkmaar–Amsterdam Centraal: final delay under 3 min on 15 of its 15 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 05:47 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November +2 min

Next service: tomorrow 00:31 from Alkmaar · Mon 23 Nov

Next departure 00:31 tomorrow · Alkmaar
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 0 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 6 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

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=7
  • 100% F n=5
  • 100% S n=1
  • 100% S n=1

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
00:31on time on time
00:36≈ on time ≈ on time
00:41≈ on time ≈ on time
00:45 / 00:48≈ on time ≈ on time
00:53≈ on time ≈ on time
00:56≈ on time ≈ on time
00:59≈ on time ≈ on time
01:02≈ on time ≈ on time
01:05≈ on time ≈ on time
01:11≈ on time ≈ on time
01:17on 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
Fri 20 Nov— 01:18+2 min+2 min
Thu 19 Nov— 01:180 min—
Wed 18 Nov— 01:180 min—
Mon 16 NovAmsterdam Sloterdijk 01:280 min—
Fri 13 Nov— 01:190 min+2 min
Thu 12 Nov— 01:590 min—
Wed 11 Nov— 01:180 min—
Tue 10 Nov— 01:180 min—
Mon 9 NovAmsterdam Sloterdijk 01:240 min—
Fri 6 Nov— 01:390 min—
Thu 5 Nov— 01:190 min—
Wed 4 Nov— 01:190 min—
Tue 3 Nov— 01:180 min—
Thu 29 Oct— 01:210 min—
Mon 26 OctAmsterdam Sloterdijk 01:260 min—
Fri 23 Oct— 01:370 min—
Thu 22 Oct— 01:180 min—
Tue 20 Oct— 01:180 min—
Mon 19 OctAmsterdam Sloterdijk 01:250 min—
Sun 18 OctAmsterdam Sloterdijk 01:420 min—
Sat 17 Oct— 01:350 min—
Fri 16 Oct— 01:180 min—
Thu 15 Oct— 01:190 min—
Wed 14 Oct— 01:190 min—
Tue 13 Oct— 01:210 min—
Mon 12 OctAmsterdam Sloterdijk 01:300 min—
Thu 8 Oct— 01:220 min—
Mon 5 OctAmsterdam Sloterdijk 01:25No data—
Mon 28 SeptAmsterdam Sloterdijk 01:28No data—
Mon 21 SeptAmsterdam Sloterdijk 01:26No data—