Train NS 2980 Amsterdam Centraal – Enkhuizen

Amsterdam Centraal 23:23 → Enkhuizen 00:23 Daily 1 h 00 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 23:23 from Amsterdam Centraal · Sat 7 Nov

Next departure 23:23 today · Amsterdam Centraal
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Enkhuizen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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:23on time on time
23:28 / 23:30≈ on time ≈ on time
23:56 / 23:58≈ on time ≈ on time
00:02≈ on time ≈ on time
00:09≈ on time ≈ on time
00:14 / 00:16≈ on time ≈ on time
00:19≈ on time ≈ on time
00:23on 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
Fri 6 Nov— 00:240 min—
Thu 5 Nov— 00:340 min—
Wed 4 Nov— 00:250 min+3 min
Tue 3 Nov— 00:240 min—
Mon 2 Nov— 00:240 min—
Sun 1 NovBovenkarspel Flora 00:330 min—
Sat 31 OctAmsterdam Bijlmer ArenA 00:240 min—
Fri 30 Oct— 00:240 min—
Thu 29 Oct— 00:250 min—
Wed 28 Oct— 00:240 min—
Tue 27 Oct— 00:250 min—
Mon 26 Oct— 00:340 min—
Sun 25 OctBovenkarspel Flora 00:340 min—
Fri 23 Oct— 23:29+2 min+2 min
Thu 22 Oct— 00:270 min—
Wed 21 Oct— 00:240 min—
Tue 20 Oct— 00:290 min—
Mon 19 Oct— 00:350 min—
Sun 18 OctBovenkarspel Flora 00:340 min—
Sat 17 OctBovenkarspel Flora 00:330 min—
Fri 16 Oct— 00:240 min—
Thu 15 Oct— 00:430 min—
Wed 14 Oct— 00:250 min+3 min
Tue 13 Oct— 00:290 min—
Mon 12 Oct— 00:250 min—
Sun 11 OctBovenkarspel Flora 00:330 min+4 min
Sat 10 OctEindhoven Centraal 00:530 min+14 min
Fri 9 Oct— 00:240 min—
Thu 8 Oct— 00:250 min—
Wed 7 Oct— 00:240 min—