Train NS 2951 Enkhuizen – Amsterdam Centraal

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

It does not run today

Last recorded run: Friday 6 November No data

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

Next departure 13:09 Friday · Enkhuizen
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 4 full · 3 partial · 3 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 6 full · 3 partial · 28 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 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

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

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 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
  • 100% 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
13:09on time on time
13:13≈ on time ≈ on time
13:16 / 13:17≈ on time ≈ on time
13:21 / 13:22≈ on time ≈ on time
13:29≈ on time ≈ +1 min
13:33 / 13:34≈ on time ≈ +1 min
13:59 / 14:04≈ on time ≈ +1 min
14:10on time +2 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 14:19No data—
Sun 1 NovAmsterdam Sloterdijk 14:19Partial coverage+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 14:18Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 14:190 min—
Sun 25 OctAmsterdam Sloterdijk 14:22No data—
Sun 18 OctAmsterdam Sloterdijk 14:20Partial coverage+1 min—
Sat 17 OctAmsterdam Sloterdijk 14:18No data—
Fri 16 OctAmsterdam Sloterdijk 14:200 min—
Sun 11 OctAmsterdam Sloterdijk 14:19+1 min+2 min
Sat 10 OctAmsterdam Sloterdijk 14:180 min—
Fri 9 OctAmsterdam Sloterdijk 14:19+2 min+2 min
Mon 5 OctSittard 16:350 min—
Fri 2 OctAmsterdam Sloterdijk 14:18No data—
Sun 27 SeptAmsterdam Sloterdijk 14:18No data—
Sat 26 SeptAmsterdam Sloterdijk 14:19No data—
Fri 25 SeptAmsterdam Sloterdijk 14:18No data—
Sun 20 SeptAmsterdam Sloterdijk 14:25No data—
Sat 19 SeptAmsterdam Sloterdijk 14:18No data—
Fri 18 SeptAmsterdam Sloterdijk 14:19No data—
Sun 13 SeptAmsterdam Sloterdijk 14:18No data—
Sat 12 SeptAmsterdam Sloterdijk 14:19No data—
Fri 11 SeptAmsterdam Sloterdijk 14:19No data—
Sun 6 SeptAmsterdam Sloterdijk 14:18No data—
Sat 5 SeptAmsterdam Sloterdijk 14:18No data—
Fri 4 SeptAmsterdam Sloterdijk 14:24No data—
Sun 30 AugAmsterdam Sloterdijk 14:19No data—
Sat 29 AugAmsterdam Sloterdijk 14:19No data—
Fri 28 AugAmsterdam Sloterdijk 14:21No data—
Sun 23 AugSittard 16:31No data—
Sat 22 AugSittard 16:31No data—