Train NS 2925 Enkhuizen – Amsterdam Centraal

Enkhuizen 06:39 → Amsterdam Centraal 07:37 Fri, Sat, Sun 0 h 58 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 07:44 +3 min

  1. Enkhuizen06:39
  2. Bovenkarspel Flora06:43
  3. Bovenkarspel-Grootebroek06:46
  4. Hoorn Kersenboogerd06:59
  5. Hoorn07:03
  6. Amsterdam Sloterdijk07:29
  7. Amsterdam Centraal07:37

Next service: Friday 06:39 from Enkhuizen · Fri 13 Nov

Next departure 06:39 Friday · Enkhuizen
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 8 full · 1 partial · 2 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 9 full · 1 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Sat 31 Oct Max en route +26 min · last fix heading to Sittard +24 min
  • Sun 8 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 67% S n=3
  • 75% S n=4

Stops and timetable

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

Last 90 days, 10 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:39on time on time
06:43≈ on time ≈ on time
06:46 / 06:47≈ on time ≈ +1 min
06:51 / 06:52≈ on time ≈ +1 min
06:59≈ on time ≈ +2 min
07:03 / 07:04≈ on time ≈ +3 min
07:29 / 07:31≈ +1 min ≈ +5 min
07:37+1 min +6 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 8 NovAmsterdam Sloterdijk 07:44Partial coverage+3 min+3 min
Fri 6 NovAmsterdam Sloterdijk 08:04No data—
Sun 1 NovArnhem Centraal 09:070 min—
Sat 31 OctSittard 10:51+24 min+26 min
Fri 30 OctAmsterdam Sloterdijk 07:49+1 min—
Sun 25 OctSittard 10:05No data—
Sun 18 OctSittard 10:04+1 min—
Sat 17 OctSittard 10:07+1 min+6 min
Fri 16 OctAmsterdam Sloterdijk 07:490 min—
Sun 11 OctEde-Wageningen 08:50+1 min—
Sat 10 OctSittard 10:040 min—
Fri 9 OctAmsterdam Sloterdijk 07:48+2 min+2 min
Mon 5 OctSittard 10:02No data—
Sun 4 OctSittard 10:01No data—
Sat 3 OctSittard 10:02No data—
Fri 2 OctAmsterdam Sloterdijk 07:50No data—
Sun 27 SeptSittard 10:03No data—
Sat 26 SeptAmsterdam Amstel 08:02No data—
Fri 25 SeptAmsterdam Sloterdijk 07:49No data—
Sun 20 SeptUtrecht Centraal 08:23No data—
Sat 19 SeptUtrecht Centraal 08:23No data—
Fri 18 SeptAmsterdam Sloterdijk 07:50No data—
Sun 13 SeptSittard 10:02No data—
Sat 12 SeptSittard 10:02No data—
Fri 11 SeptAmsterdam Sloterdijk 07:48No data—
Sun 6 SeptWeert 09:31No data—
Sat 5 SeptWeert 09:31No data—
Fri 4 SeptAmsterdam Sloterdijk 07:48No data—
Sun 30 AugSittard 10:03No data—
Sat 29 AugSittard 10:12No data—