Train NS 2981 Enkhuizen – Amsterdam Centraal

Enkhuizen 20:39 → Amsterdam Centraal 21:36 Daily 0 h 57 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

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

Next departure 20:39 today · Enkhuizen
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 1 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 18 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: +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

  • Tue 6 Oct Max en route +3 min · last fix heading to — +3 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 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 80% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=3
  • 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
20:39on time on time
20:43≈ on time ≈ on time
20:46 / 20:47≈ on time ≈ on time
20:51 / 20:52≈ on time ≈ on time
20:59≈ on time ≈ +1 min
21:03 / 21:04≈ on time ≈ +1 min
21:29 / 21:31≈ on time ≈ +2 min
21:36on time +2 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:190 min+14 min
Thu 5 Nov— 00:040 min—
Wed 4 Nov— 00:040 min—
Tue 3 Nov— 00:080 min—
Mon 2 Nov— 00:09+2 min+3 min
Sun 1 NovAmsterdam Sloterdijk 21:480 min—
Sat 31 OctWeert 00:050 min—
Fri 30 Oct— 21:090 min—
Thu 29 Oct— 00:260 min+12 min
Tue 27 Oct— 00:040 min—
Mon 26 Oct— 00:070 min—
Sun 25 OctAmsterdam Sloterdijk 21:48No data—
Fri 23 Oct— 00:020 min—
Thu 22 Oct— 00:050 min—
Wed 21 Oct— 00:010 min—
Tue 20 Oct— 23:500 min—
Mon 19 Oct— 00:07+1 min+2 min
Sun 18 OctAmsterdam Sloterdijk 21:480 min—
Sat 17 OctSittard 00:040 min—
Fri 16 Oct— 00:04+2 min+2 min
Thu 15 Oct— 00:050 min—
Wed 14 Oct— 00:130 min+3 min
Tue 13 Oct— 00:050 min—
Mon 12 Oct— 00:040 min—
Sun 11 OctAmsterdam Sloterdijk 21:490 min—
Sat 10 OctAmsterdam Amstel 00:050 min—
Fri 9 Oct— 00:09+2 min+4 min
Wed 7 Oct— 00:450 min+20 min
Tue 6 Oct— 00:04+3 min+3 min
Mon 5 Oct— 00:050 min—