Train NS 2924 Amsterdam Centraal – Enkhuizen

Amsterdam Centraal 09:23 → Enkhuizen 10:23 Fri, Sat, Sun 1 h 00 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Bovenkarspel Flora at 10:34 0 min

  1. Amsterdam Centraal09:23
  2. Amsterdam Sloterdijk09:28
  3. Hoorn09:56
  4. Hoogkarspel10:09
  5. Bovenkarspel-Grootebroek10:14
  6. Bovenkarspel Flora10:19
  7. Enkhuizen10:23

Next service: Friday 09:23 from Amsterdam Centraal · Fri 13 Nov

Next departure 09:23 Friday · Amsterdam Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 2 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Enkhuizen, 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 10 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
09:23on time on time
09:28 / 09:30≈ on time ≈ on time
09:56 / 09:58≈ on time ≈ +1 min
10:02≈ on time ≈ +1 min
10:09≈ on time ≈ +1 min
10:14 / 10:16≈ on time ≈ +1 min
10:19≈ on time ≈ +1 min
10:23on time +1 min

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 8 NovBovenkarspel Flora 10:34Partial coverage0 min—
Fri 6 NovBovenkarspel Flora 10:33No data—
Sun 1 NovDen Helder Zuid 11:09+2 min+2 min
Sat 31 OctBovenkarspel Flora 10:34+1 min—
Fri 30 OctBovenkarspel Flora 10:470 min—
Sun 25 OctBovenkarspel Flora 10:34No data—
Sun 18 OctBovenkarspel Flora 10:34+1 min—
Sat 17 OctBovenkarspel Flora 10:340 min+1 min
Fri 16 OctBovenkarspel Flora 10:340 min—
Sun 11 OctBovenkarspel Flora 10:34+1 min—
Sat 10 OctBovenkarspel Flora 10:340 min—
Fri 9 OctBovenkarspel Flora 10:340 min—
Mon 5 OctBovenkarspel Flora 10:34No data—
Sun 4 OctBovenkarspel Flora 10:34No data—
Sat 3 OctDuivendrecht 09:40No data—
Fri 2 OctBovenkarspel Flora 10:33No data—
Sun 27 SeptBovenkarspel Flora 10:34No data—
Sat 26 SeptBovenkarspel Flora 10:34No data—
Fri 25 SeptBovenkarspel Flora 10:34No data—
Sun 20 SeptBovenkarspel Flora 10:34No data—
Sat 19 SeptBovenkarspel Flora 10:33No data—
Fri 18 SeptBovenkarspel Flora 10:34No data—
Sun 13 SeptBovenkarspel Flora 10:34No data—
Sat 12 SeptBovenkarspel Flora 10:47No data—
Fri 11 SeptBovenkarspel Flora 10:34No data—
Sun 6 SeptBovenkarspel Flora 10:34No data—
Sat 5 SeptBovenkarspel Flora 10:35No data—
Fri 4 SeptBovenkarspel Flora 10:33No data—
Sun 30 AugBovenkarspel Flora 10:34No data—
Sat 29 AugBovenkarspel Flora 10:34No data—