Train NS 2928 Amsterdam Centraal – Enkhuizen

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 10:18 from Amsterdam Centraal · Fri 13 Nov

Next departure 10:18 Friday · Amsterdam Centraal
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 2 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 26 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: +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

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

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% S n=3
  • 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
10:18on time on time
10:23 / 10:30≈ on time ≈ on time
10:56 / 10:58≈ on time ≈ on time
11:02≈ on time ≈ on time
11:09≈ on time ≈ on time
11:14 / 11:16≈ on time ≈ on time
11:19≈ on time ≈ on time
11:23on 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 6 NovBovenkarspel Flora 11:33No data—
Sun 1 NovDen Helder Zuid 12:10Partial coverage+1 min+1 min
Sat 31 OctBovenkarspel Flora 11:330 min—
Fri 30 OctBovenkarspel Flora 11:340 min—
Sun 25 OctBovenkarspel Flora 11:34No data—
Sun 18 OctBovenkarspel Flora 11:340 min—
Sat 17 OctBovenkarspel Flora 11:340 min—
Fri 16 OctBovenkarspel Flora 11:360 min—
Sun 11 OctBovenkarspel Flora 11:330 min+2 min
Sat 10 OctBovenkarspel Flora 11:330 min—
Fri 9 OctBovenkarspel Flora 11:330 min+2 min
Mon 5 OctBovenkarspel Flora 11:34No data—
Sun 4 OctBovenkarspel Flora 11:33No data—
Fri 2 OctBovenkarspel Flora 11:33No data—
Sun 27 SeptBovenkarspel Flora 11:33No data—
Sat 26 SeptBovenkarspel Flora 11:34No data—
Fri 25 SeptBovenkarspel Flora 11:34No data—
Sun 20 SeptBovenkarspel Flora 11:34No data—
Sat 19 SeptBovenkarspel Flora 11:33No data—
Fri 18 SeptBovenkarspel Flora 11:34No data—
Sun 13 SeptBovenkarspel Flora 11:34No data—
Sat 12 SeptBovenkarspel Flora 11:33No data—
Fri 11 SeptBovenkarspel Flora 11:34No data—
Sun 6 SeptBovenkarspel Flora 11:33No data—
Sat 5 SeptBovenkarspel Flora 11:34No data—
Fri 4 SeptBovenkarspel Flora 11:34No data—
Sun 30 AugBovenkarspel Flora 11:35No data—
Sat 29 AugBovenkarspel Flora 11:33No data—
Fri 28 AugBovenkarspel Flora 11:34No data—
Sun 23 AugBovenkarspel Flora 11:34No data—