Train NS 2987 Enkhuizen – Amsterdam Centraal

Enkhuizen 22:09 → Amsterdam Centraal 23:07 Daily 0 h 58 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +2 min

Next service: today 22:09 from Enkhuizen · Sun 8 Nov

Full trip card
Next departure 22:09 today · Enkhuizen
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 23 full · 1 partial · 3 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 19 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: +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

  • Fri 16 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
Enkhuizen
22:09on time on time
Bovenkarspel Flora
22:13≈ on time ≈ on time
Bovenkarspel-Grootebroek
22:16 / 22:17≈ on time ≈ on time
Hoogkarspel
22:21 / 22:22≈ on time ≈ on time
Hoorn Kersenboogerd
22:29≈ on time ≈ +1 min
Hoorn
22:33 / 22:34≈ on time ≈ +1 min
Amsterdam Sloterdijk
22:59 / 23:01≈ on time ≈ +1 min
Amsterdam Centraal
23:07on time on time

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
Sat 7 NovAmsterdam Sloterdijk 23:14Partial coverage+2 min+2 min
Fri 6 Nov— 00:290 min—
Thu 5 Nov— 00:290 min—
Wed 4 Nov— 00:490 min+8 min
Tue 3 Nov— 00:290 min—
Sun 1 NovAmsterdam Amstel 23:390 min—
Sat 31 OctAmsterdam Bijlmer ArenA 00:300 min—
Fri 30 Oct— 00:520 min—
Thu 29 Oct— 00:400 min+3 min
Wed 28 Oct— 00:480 min—
Tue 27 Oct— 00:400 min—
Mon 26 Oct— 00:290 min—
Sun 25 Oct's-Hertogenbosch 00:30No data—
Fri 23 Oct— 23:38+4 min+4 min
Thu 22 Oct— 00:290 min—
Wed 21 Oct— 00:520 min—
Tue 20 Oct— 00:340 min—
Mon 19 Oct— 22:34No data—
Sun 18 Oct's-Hertogenbosch 00:30+1 min+2 min
Sat 17 Oct's-Hertogenbosch 00:290 min—
Fri 16 Oct— 00:40+5 min+5 min
Thu 15 Oct— 00:400 min—
Wed 14 Oct— 00:290 min+11 min
Tue 13 Oct— 00:52No data—
Mon 12 Oct— 00:300 min—
Sun 11 OctEde-Wageningen 00:330 min+9 min
Sat 10 Oct— 01:220 min+19 min
Fri 9 Oct— 00:290 min—
Thu 8 Oct— 00:290 min—
Wed 7 Oct— 00:300 min+3 min