Train NS 3727 Enkhuizen – Amsterdam Centraal

Enkhuizen 06:55 → Amsterdam Centraal 07:54 Mon, Tue, Wed, Thu 0 h 59 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:55 from Enkhuizen · Thu 5 Nov

Next departure 06:55 today · Enkhuizen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 7 full · 9 partial · 1 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 7 full · 10 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Tue 6 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 100% W n=5
  • 100% T n=4
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 17 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
06:55on time on time
06:59≈ on time ≈ on time
07:03≈ on time ≈ on time
07:08 / 07:09≈ on time ≈ on time
07:16≈ on time ≈ on time
07:20 / 07:21≈ on time ≈ on time
07:33≈ on time ≈ on time
07:48≈ on time ≈ +1 min
07:54on 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
Wed 4 NovAmsterdam Sloterdijk 08:02Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 08:04Partial coverage+2 min+2 min
Mon 2 NovAmsterdam Sloterdijk 08:04No data—
Thu 29 OctAmsterdam Sloterdijk 14:270 min—
Wed 28 OctAmsterdam Sloterdijk 08:04Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 08:02Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 08:02Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 08:06Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 08:03Partial coverage0 min—
Tue 20 OctAmsterdam Sloterdijk 08:020 min—
Mon 19 OctAmsterdam Sloterdijk 08:030 min—
Thu 15 OctAmsterdam Sloterdijk 08:07+2 min+2 min
Wed 14 OctAmsterdam Sloterdijk 08:030 min—
Tue 13 OctAmsterdam Sloterdijk 08:030 min—
Mon 12 OctAmsterdam Sloterdijk 08:020 min—
Thu 8 OctAmsterdam Sloterdijk 08:04Partial coverage+2 min+2 min
Wed 7 OctAmsterdam Sloterdijk 08:02Partial coverage+1 min—
Tue 6 OctAmsterdam Sloterdijk 08:05Partial coverage+3 min+3 min
Thu 1 OctAmsterdam Sloterdijk 08:02No data—
Wed 30 SeptAmsterdam Sloterdijk 08:13No data—
Tue 29 SeptAmsterdam Sloterdijk 08:03No data—
Mon 28 SeptAmsterdam Sloterdijk 08:03No data—
Thu 24 SeptAmsterdam Sloterdijk 08:02No data—
Wed 23 SeptAmsterdam Sloterdijk 08:03No data—
Tue 22 SeptAmsterdam Sloterdijk 08:03No data—
Mon 21 SeptAmsterdam Sloterdijk 08:02No data—
Thu 17 SeptAmsterdam Sloterdijk 08:03No data—
Wed 16 SeptAmsterdam Sloterdijk 08:03No data—
Tue 15 SeptAmsterdam Sloterdijk 08:04No data—
Mon 14 SeptAmsterdam Sloterdijk 08:02No data—