Train NS 3064 Nijmegen – Heerhugowaard

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 18:13 from Nijmegen · Thu 19 Nov

Next departure 18:13 today · Nijmegen
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 24 full · 2 partial · 2 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 47 full · 2 partial · 23 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 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

  • Tue 10 Nov Max en route +12 min · last fix heading to Nijmegen +9 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 92% · 45
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 80% T n=5
  • 86% W n=7
  • 100% T n=5
  • 100% F n=6
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 49 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:13on time on time
18:26 / 18:31≈ on time ≈ on time
18:41≈ on time ≈ on time
18:58≈ on time ≈ +1 min
19:06 / 19:09≈ on time ≈ +1 min
19:28≈ on time ≈ +1 min
19:35 / 19:39≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:52≈ on time ≈ +1 min
20:04≈ on time ≈ +1 min
20:10≈ on time ≈ +1 min
20:16 / 20:19≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:28on 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
Wed 18 NovEde-Wageningen 20:29Partial coverage0 min—
Tue 17 NovNijmegen 20:32Partial coverage+1 min+2 min
Mon 16 NovNijmegen 20:290 min+2 min
Sun 15 NovAlkmaar Noord 20:38+2 min+2 min
Sat 14 NovAlkmaar Noord 20:37+1 min—
Fri 13 NovEde-Wageningen 20:240 min—
Thu 12 NovNijmegen 20:19+1 min—
Wed 11 NovNijmegen 20:240 min+3 min
Tue 10 NovNijmegen 20:39+9 min+12 min
Mon 9 NovNijmegen 20:190 min—
Sun 8 NovDen Helder Zuid 21:070 min+1 min
Sat 7 NovDen Helder Zuid 21:04+1 min+1 min
Fri 6 NovEde-Wageningen 21:02+2 min+8 min
Thu 5 NovNijmegen 20:580 min—
Wed 4 NovNijmegen 20:59+1 min—
Tue 3 Nov— 20:580 min—
Sun 1 NovDen Helder Zuid 21:12+1 min—
Sat 31 OctDen Helder Zuid 21:070 min—
Fri 30 OctVeenendaal-De Klomp 20:570 min—
Thu 29 Oct— 20:570 min—
Wed 28 Oct— 20:570 min—
Tue 27 Oct— 20:580 min—
Mon 26 OctAmsterdam Sloterdijk 20:580 min—
Sun 25 OctDen Helder Zuid 21:07No data—
Sat 24 OctDen Helder Zuid 21:110 min—
Fri 23 OctAmsterdam Amstel 20:570 min—
Thu 22 Oct— 21:25No data—
Wed 21 Oct— 21:140 min—
Mon 19 OctEde-Wageningen 20:570 min—
Sun 18 OctDen Helder Zuid 21:060 min—