Train NS 3066 Nijmegen – Heerhugowaard

Nijmegen 18:43 → Heerhugowaard 20:58 Daily 2 h 15 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 18:58 0 min

  1. Nijmegen18:43
  2. Ede-Wageningen19:11
  3. Utrecht Centraal19:36
  4. Amsterdam Sloterdijk20:14
  5. Castricum20:34
  6. Alkmaar20:46
  7. Heerhugowaard20:58

Next service: tomorrow 18:43 from Nijmegen · Tue 17 Nov

Next departure 18:43 tomorrow · Nijmegen
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 2 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 21 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: +2 min

Last 30 days

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

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

Worst days

  • Sun 11 Oct Max en route +16 min · last fix heading to Den Helder Zuid +16 min
  • Mon 2 Nov Max en route +16 min · last fix heading to — +16 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 93% · 42
  • 3–10 min 0% · 0
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=4
  • 100% W n=5
  • 100% T n=7
  • 100% F n=7
  • 100% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 45 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
18:43on time on time
18:56 / 19:01≈ on time ≈ on time
19:11≈ on time ≈ on time
19:28≈ on time ≈ +1 min
19:36 / 19:39≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:05 / 20:09≈ on time ≈ +1 min
20:14≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:40≈ on time ≈ +2 min
20:46 / 20:49≈ on time ≈ +2 min
20:53≈ on time ≈ +2 min
20:58on 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
Mon 16 Nov— 18:580 min—
Sun 15 NovAlkmaar Noord 21:09+3 min+3 min
Sat 14 NovAlkmaar Noord 21:09+2 min+2 min
Fri 13 NovNijmegen 20:490 min+1 min
Thu 12 Nov— 20:53+1 min+2 min
Wed 11 Nov— 20:540 min+2 min
Mon 9 Nov— 20:49+1 min—
Sun 8 NovDen Helder Zuid 21:37+1 min—
Sat 7 NovDen Helder Zuid 21:340 min—
Fri 6 NovNijmegen 21:29+2 min+2 min
Thu 5 Nov— 21:280 min—
Wed 4 Nov— 21:28+1 min+1 min
Mon 2 Nov— 21:58+16 min+16 min
Sun 1 NovDen Helder Zuid 21:34+2 min+2 min
Sat 31 OctDen Helder Zuid 22:00+2 min+2 min
Fri 30 Oct— 21:340 min—
Thu 29 Oct— 21:270 min—
Wed 28 Oct— 21:280 min—
Tue 27 Oct— 21:300 min—
Mon 26 OctUtrecht Centraal 21:27No data—
Sun 25 OctDen Helder Zuid 21:37No data—
Sat 24 OctDen Helder Zuid 21:360 min—
Fri 23 OctDriebergen-Zeist 21:280 min—
Thu 22 Oct— 21:560 min—
Wed 21 Oct— 21:290 min—
Tue 20 Oct— 21:280 min—
Mon 19 OctNijmegen 21:280 min—
Sun 18 OctDen Helder Zuid 21:37+1 min+1 min
Sat 17 OctDen Helder Zuid 22:070 min—
Fri 16 OctUtrecht Centraal 21:17+1 min+2 min