Train NS 2912 Amsterdam Centraal – Enkhuizen

Amsterdam Centraal 06:22 → Enkhuizen 07:23 Mon, Tue, Wed, Thu, Fri 1 h 01 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Bovenkarspel Flora at 07:34 +1 min

  1. Amsterdam Centraal06:22
  2. Amsterdam Sloterdijk06:27
  3. Hoorn06:55
  4. Hoogkarspel07:09
  5. Bovenkarspel-Grootebroek07:14
  6. Bovenkarspel Flora07:19
  7. Enkhuizen07:23

Next service: tomorrow 06:22 from Amsterdam Centraal · Tue 10 Nov

Next departure 06:22 tomorrow · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 1 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 13 full · 10 partial · 39 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 Enkhuizen, 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 3 Nov Max en route +5 min · last fix heading to Bovenkarspel Flora +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 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=5
  • 100% T n=5
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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:22on time on time
06:27 / 06:28≈ on time ≈ on time
06:55 / 06:58≈ on time ≈ +1 min
07:02≈ on time ≈ +1 min
07:09≈ on time ≈ +1 min
07:14 / 07:16≈ on time ≈ +1 min
07:19≈ on time ≈ +1 min
07:23on 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
Mon 9 NovBovenkarspel Flora 07:34Partial coverage+1 min—
Fri 6 NovBovenkarspel Flora 07:34No data—
Thu 5 NovBovenkarspel Flora 07:34Partial coverage0 min—
Wed 4 NovBovenkarspel Flora 07:340 min—
Tue 3 NovBovenkarspel Flora 07:34+3 min+5 min
Mon 2 NovBovenkarspel Flora 07:34Partial coverage0 min—
Fri 30 OctBovenkarspel Flora 07:340 min—
Thu 29 OctBovenkarspel Flora 07:34Partial coverage0 min—
Wed 28 OctBovenkarspel Flora 07:34Partial coverage+1 min+3 min
Tue 27 OctBovenkarspel Flora 07:330 min—
Mon 26 OctBovenkarspel Flora 07:34Partial coverage+1 min—
Thu 22 OctBovenkarspel Flora 07:340 min—
Wed 21 OctBovenkarspel Flora 07:340 min—
Tue 20 OctBovenkarspel Flora 07:33+1 min+1 min
Mon 19 OctBovenkarspel Flora 07:340 min—
Fri 16 OctBovenkarspel Flora 07:340 min—
Thu 15 OctBovenkarspel Flora 07:34Partial coverage+3 min+4 min
Wed 14 OctBovenkarspel Flora 07:34Partial coverage+1 min—
Tue 13 OctBovenkarspel Flora 07:34Partial coverage0 min—
Mon 12 OctBovenkarspel Flora 07:340 min—
Fri 9 OctBovenkarspel Flora 07:35+1 min—
Thu 8 OctBovenkarspel Flora 07:34Partial coverage+1 min+30 min
Wed 7 OctBovenkarspel Flora 07:340 min—
Tue 6 OctBovenkarspel Flora 07:340 min—
Mon 5 OctBovenkarspel Flora 07:35No data—
Fri 2 OctBovenkarspel Flora 07:34No data—
Thu 1 OctBovenkarspel Flora 07:34No data—
Wed 30 SeptBovenkarspel Flora 07:33No data—
Tue 29 SeptBovenkarspel Flora 07:34No data—
Mon 28 SeptBovenkarspel Flora 07:34No data—