Train NS 2993 Enkhuizen – Amsterdam Centraal

Enkhuizen 23:39 → Amsterdam Centraal 00:45 Daily 1 h 06 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 23:39 from Enkhuizen · Sat 7 Nov

Next departure 23:39 today · Enkhuizen
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 20 full · 4 partial · 1 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 24 full · 4 partial · 12 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: +1 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

  • Mon 19 Oct Max en route +9 min · last fix heading to — +9 min
  • Sat 10 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
23:39on time on time
23:43≈ on time ≈ on time
23:46 / 23:47≈ on time ≈ on time
23:51 / 23:52≈ on time ≈ on time
23:59≈ on time ≈ on time
00:03 / 00:04≈ on time ≈ on time
00:16≈ on time ≈ +1 min
00:19≈ on time ≈ +1 min
00:22≈ on time ≈ +1 min
00:29≈ on time ≈ +1 min
00:33≈ on time ≈ +1 min
00:40≈ on time ≈ +1 min
00:45on 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
Fri 6 Nov— 00:440 min—
Thu 5 Nov— 00:440 min—
Wed 4 Nov— 00:440 min—
Tue 3 Nov— 00:440 min—
Sun 1 NovAmsterdam Sloterdijk 00:54Partial coverage0 min—
Sat 31 Oct— 00:540 min—
Fri 30 Oct— 00:460 min—
Wed 28 Oct— 00:470 min—
Tue 27 Oct— 00:460 min—
Mon 26 Oct— 00:490 min—
Sun 25 OctAmsterdam Sloterdijk 00:55Partial coverage0 min—
Thu 22 Oct— 00:460 min—
Wed 21 Oct— 00:470 min—
Tue 20 Oct— 00:46No data—
Mon 19 Oct— 01:03+9 min+9 min
Sun 18 OctAmsterdam Sloterdijk 01:170 min—
Sat 17 OctAmsterdam Sloterdijk 00:54Partial coverage0 min—
Fri 16 Oct— 00:49+2 min+2 min
Thu 15 Oct— 00:460 min—
Wed 14 Oct— 00:460 min—
Tue 13 Oct— 00:460 min—
Mon 12 Oct— 00:460 min—
Sun 11 OctAmsterdam Sloterdijk 00:54Partial coverage0 min—
Sat 10 Oct— 00:57+6 min+6 min
Fri 9 Oct— 00:460 min—
Thu 8 Oct— 00:470 min—
Wed 7 Oct— 00:490 min—
Tue 6 Oct— 00:460 min—
Mon 5 OctHoorn 00:460 min—
Sun 4 OctAmsterdam Sloterdijk 00:53No data—