Train NS 2963 Enkhuizen – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 17:18 0 min

  1. Enkhuizen16:09
  2. Bovenkarspel Flora16:13
  3. Bovenkarspel-Grootebroek16:16
  4. Hoorn Kersenboogerd16:29
  5. Hoorn16:33
  6. Amsterdam Sloterdijk16:59
  7. Amsterdam Centraal17:10

Next service: Friday 16:09 from Enkhuizen · Fri 13 Nov

Next departure 16:09 Friday · Enkhuizen
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 4 full · 4 partial · 3 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 5 full · 4 partial · 29 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: +2 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 9 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
16:09on time on time
16:13≈ on time ≈ +1 min
16:16 / 16:17≈ on time ≈ +1 min
16:21 / 16:22≈ on time ≈ +1 min
16:29≈ on time ≈ +1 min
16:33 / 16:34≈ on time ≈ +1 min
16:59 / 17:04≈ on time ≈ on time
17:10on 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
Fri 6 NovAmsterdam Sloterdijk 17:18Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 17:23Partial coverage+4 min+5 min
Sat 31 OctAmsterdam Sloterdijk 17:18Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 17:18No data—
Sun 25 OctAmsterdam Sloterdijk 17:19No data—
Sun 18 OctAmsterdam Sloterdijk 17:19Partial coverage+1 min—
Sat 17 OctAmsterdam Sloterdijk 17:18No data—
Fri 16 OctAmsterdam Sloterdijk 17:200 min—
Sun 11 OctAmsterdam Sloterdijk 17:180 min+2 min
Sat 10 OctAmsterdam Sloterdijk 17:19+1 min—
Fri 9 OctAmsterdam Sloterdijk 17:19+1 min—
Mon 5 Oct's-Hertogenbosch 19:340 min+1 min
Fri 2 OctAmsterdam Sloterdijk 17:20No data—
Sun 27 SeptAmsterdam Sloterdijk 17:18No data—
Sat 26 SeptAmsterdam Sloterdijk 17:18No data—
Fri 25 SeptAmsterdam Sloterdijk 17:19No data—
Sun 20 SeptAmsterdam Sloterdijk 17:20No data—
Sat 19 SeptAmsterdam Sloterdijk 17:19No data—
Fri 18 SeptAmsterdam Sloterdijk 17:19No data—
Sun 13 SeptAmsterdam Sloterdijk 17:18No data—
Sat 12 SeptAmsterdam Sloterdijk 17:19No data—
Fri 11 SeptAmsterdam Sloterdijk 17:18No data—
Sun 6 SeptAmsterdam Sloterdijk 17:18No data—
Sat 5 SeptAmsterdam Sloterdijk 17:18No data—
Fri 4 SeptAmsterdam Sloterdijk 17:20No data—
Sun 30 AugAmsterdam Sloterdijk 17:18No data—
Sat 29 AugAmsterdam Sloterdijk 17:22No data—
Fri 28 AugAmsterdam Sloterdijk 17:18No data—
Sun 23 AugSittard 19:31No data—
Sat 22 AugSittard 19:32No data—