Train NS 2962 Amsterdam Centraal – Enkhuizen

Amsterdam Centraal 18:48 → Enkhuizen 19:53 Fri, Sat, Sun 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 18:48 from Amsterdam Centraal · Fri 6 Nov

Next departure 18:48 tomorrow · Amsterdam Centraal
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%
8/8 runs under 3 min
RT coverage: 5 full · 3 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: +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

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

  • Early 0% · 0
  • On time 100% · 8
  • 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=2
  • 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, 8 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
18:48on time on time
18:53 / 19:00≈ on time ≈ on time
19:26 / 19:28≈ on time ≈ on time
19:32≈ on time ≈ on time
19:39≈ on time ≈ on time
19:44 / 19:46≈ on time ≈ on time
19:49≈ on time ≈ on time
19:53on 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 1 NovBovenkarspel Flora 20:04Partial coverage0 min—
Sat 31 OctBovenkarspel Flora 20:04Partial coverage0 min—
Fri 30 OctAmsterdam Centraal 19:54No data—
Sun 25 OctBovenkarspel Flora 20:04No data—
Sun 18 OctBovenkarspel Flora 20:04Partial coverage+1 min—
Sat 17 OctBovenkarspel Flora 20:04No data—
Fri 16 OctBovenkarspel Flora 20:030 min—
Sun 11 OctBovenkarspel Flora 20:04+1 min—
Sat 10 OctBovenkarspel Flora 20:030 min—
Fri 9 Oct— 19:540 min—
Mon 5 Oct's-Hertogenbosch 19:540 min—
Fri 2 OctAmsterdam Centraal 19:02No data—
Sun 27 SeptBovenkarspel Flora 20:04No data—
Sat 26 SeptBovenkarspel Flora 20:04No data—
Sun 20 SeptBovenkarspel Flora 20:03No data—
Sat 19 SeptBovenkarspel Flora 20:04No data—
Fri 18 SeptAmsterdam Centraal 19:02No data—
Sun 13 SeptBovenkarspel Flora 20:04No data—
Sat 12 SeptBovenkarspel Flora 20:04No data—
Fri 11 SeptAmsterdam Centraal 19:02No data—
Sun 6 SeptBovenkarspel Flora 20:04No data—
Sat 5 SeptBovenkarspel Flora 20:04No data—
Fri 4 SeptAmsterdam Centraal 19:02No data—
Sun 30 AugBovenkarspel Flora 20:03No data—
Sat 29 AugBovenkarspel Flora 20:03No data—
Fri 28 AugHoorn 19:42No data—
Sun 23 AugBovenkarspel Flora 20:04No data—
Sat 22 AugBovenkarspel Flora 20:04No data—
Fri 21 AugBovenkarspel Flora 20:03No data—
Sun 16 AugBovenkarspel Flora 20:04No data—