Train NS 3729 Enkhuizen – Amsterdam Centraal

Enkhuizen 07:25 → Amsterdam Centraal 08:24 Mon, Tue, Wed, Thu 0 h 59 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 08:32 0 min

  1. Enkhuizen07:25
  2. Bovenkarspel Flora07:29
  3. Hoogkarspel07:38
  4. Hoorn Kersenboogerd07:46
  5. Hoorn07:50
  6. Amsterdam Sloterdijk08:18
  7. Amsterdam Centraal08:24

Next service: tomorrow 07:25 from Enkhuizen · Tue 10 Nov

Next departure 07:25 tomorrow · Enkhuizen
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 1 full · 9 partial · 7 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 35 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: 0 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 75% W n=4
  • 100% T n=3
  • — 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, 13 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
07:25on time on time
07:29— —
07:33— —
07:38 / 07:39— —
07:46— —
07:50 / 07:51— —
08:03— —
08:18— —
08:24— —

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
Mon 9 NovAmsterdam Sloterdijk 08:32Partial coverage0 min—
Thu 5 NovAmsterdam Sloterdijk 08:37No data—
Wed 4 NovAmsterdam Sloterdijk 08:34Partial coverage+4 min+4 min
Tue 3 NovAmsterdam Sloterdijk 08:32No data—
Mon 2 NovAmsterdam Sloterdijk 08:32No data—
Thu 29 OctAmsterdam Sloterdijk 08:33Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 08:34Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 08:32Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 08:32Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 08:32Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 08:32No data—
Tue 20 OctAmsterdam Sloterdijk 08:34Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 08:37Partial coverage0 min—
Thu 15 OctAmsterdam Sloterdijk 08:32No data—
Wed 14 OctHoorn 08:590 min—
Tue 13 OctAmsterdam Sloterdijk 08:32No data—
Mon 12 OctAmsterdam Sloterdijk 08:32No data—
Thu 8 OctAmsterdam Sloterdijk 08:33Partial coverage+2 min+2 min
Wed 7 OctAmsterdam Sloterdijk 08:32Partial coverage0 min—
Tue 6 OctAmsterdam Sloterdijk 08:33Partial coverage+1 min—
Thu 1 OctAmsterdam Sloterdijk 08:34No data—
Wed 30 SeptAmsterdam Sloterdijk 08:33No data—
Tue 29 SeptAmsterdam Sloterdijk 08:35No data—
Mon 28 SeptAmsterdam Sloterdijk 08:33No data—
Thu 24 SeptAmsterdam Sloterdijk 08:32No data—
Wed 23 SeptAmsterdam Sloterdijk 08:32No data—
Tue 22 SeptAmsterdam Sloterdijk 08:34No data—
Mon 21 SeptAmsterdam Sloterdijk 08:32No data—
Thu 17 SeptAmsterdam Sloterdijk 08:33No data—
Wed 16 SeptAmsterdam Sloterdijk 08:37No data—