Train NS 2937 Enkhuizen – Amsterdam Centraal

Enkhuizen 09:39 → Amsterdam Centraal 10:40 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 09:39 from Enkhuizen · Fri 13 Nov

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

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

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=3
  • 100% S n=2

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
09:39on time on time
09:43≈ on time ≈ on time
09:46 / 09:47≈ on time ≈ on time
09:51 / 09:52≈ on time ≈ on time
09:59≈ on time ≈ +1 min
10:03 / 10:04≈ +1 min ≈ +1 min
10:29 / 10:34≈ +1 min ≈ +2 min
10:40+1 min +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 10:49No data—
Sat 31 OctAmsterdam Sloterdijk 10:49Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 10:49No data—
Sun 25 OctAmsterdam Sloterdijk 10:49No data—
Sun 18 OctAmsterdam Sloterdijk 10:49Partial coverage+1 min—
Sat 17 OctAmsterdam Sloterdijk 10:49Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 10:490 min—
Sun 11 OctAmsterdam Sloterdijk 10:49+1 min+1 min
Sat 10 OctAmsterdam Sloterdijk 10:49+2 min+2 min
Fri 9 OctAmsterdam Sloterdijk 10:51+2 min+3 min
Mon 5 OctSittard 13:050 min+1 min
Fri 2 OctAmsterdam Sloterdijk 10:49No data—
Sun 27 SeptAmsterdam Sloterdijk 10:48No data—
Sat 26 SeptAmsterdam Sloterdijk 10:48No data—
Fri 25 SeptAmsterdam Sloterdijk 10:49No data—
Sun 20 SeptAmsterdam Sloterdijk 10:48No data—
Sat 19 SeptAmsterdam Sloterdijk 10:49No data—
Fri 18 SeptAmsterdam Sloterdijk 10:49No data—
Sun 13 SeptAmsterdam Sloterdijk 10:52No data—
Sat 12 SeptAmsterdam Sloterdijk 10:49No data—
Fri 11 SeptAmsterdam Sloterdijk 10:49No data—
Sun 6 SeptAmsterdam Sloterdijk 10:49No data—
Sat 5 SeptAmsterdam Sloterdijk 10:49No data—
Fri 4 SeptAmsterdam Sloterdijk 10:49No data—
Sun 30 AugAmsterdam Sloterdijk 10:50No data—
Sat 29 AugAmsterdam Sloterdijk 10:49No data—
Fri 28 AugAmsterdam Sloterdijk 10:48No data—
Sun 23 AugSittard 13:10No data—
Sat 22 AugSittard 13:10No data—
Fri 21 AugSittard 13:02No data—