Train NS 3034 Nijmegen – Heerhugowaard

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

✓ Today’s run finished

Today, last fix heading to Alkmaar Noord at 13:07 0 min

  1. Nijmegen10:43
  2. Ede-Wageningen11:11
  3. Utrecht Centraal11:36
  4. Amsterdam Sloterdijk12:14
  5. Castricum12:34
  6. Alkmaar Noord12:53
  7. Heerhugowaard12:58

Next service: tomorrow 10:43 from Nijmegen · Fri 20 Nov

Next departure 10:43 tomorrow · Nijmegen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 19 full · 4 partial · 7 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 33 full · 4 partial · 52 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: +1 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

  • Sat 10 Oct Max en route +15 min · last fix heading to Den Helder Zuid +15 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Den Helder Zuid +6 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Den Helder Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
10:43on time on time
10:56 / 11:01≈ on time ≈ on time
11:11≈ on time ≈ on time
11:28≈ on time ≈ on time
11:36 / 11:39≈ on time ≈ on time
11:58≈ on time ≈ on time
12:05 / 12:09≈ on time ≈ +1 min
12:14≈ on time ≈ +1 min
12:22≈ on time ≈ +1 min
12:34≈ on time ≈ +1 min
12:40≈ on time ≈ +1 min
12:46 / 12:49≈ on time ≈ +1 min
12:53≈ on time ≈ +1 min
12:58on 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
Thu 19 NovAlkmaar Noord 13:07Partial coverage0 min—
Wed 18 NovAlkmaar Noord 13:07Partial coverage0 min+1 min
Tue 17 NovAlkmaar Noord 13:07Partial coverage+1 min—
Mon 16 NovAlkmaar Noord 13:09Partial coverage+1 min+1 min
Sun 15 NovAlkmaar Noord 13:07+1 min—
Sat 14 NovAlkmaar Noord 13:070 min—
Fri 13 NovHeiloo 13:090 min—
Thu 12 NovHeiloo 12:540 min—
Wed 11 NovHeiloo 12:57+1 min—
Tue 10 NovHeiloo 12:540 min—
Mon 9 NovHeiloo 12:540 min—
Sun 8 NovDen Helder Zuid 13:37+6 min+6 min
Sat 7 NovDen Helder Zuid 13:37+1 min+2 min
Fri 6 NovDen Helder Zuid 13:34No data—
Thu 5 NovDen Helder Zuid 13:34No data—
Wed 4 NovDen Helder Zuid 13:370 min—
Tue 3 NovDen Helder Zuid 13:37No data—
Mon 2 NovDen Helder Zuid 13:340 min—
Sun 1 NovCastricum 13:140 min—
Sat 31 OctDen Helder Zuid 13:360 min—
Fri 30 OctDen Helder Zuid 13:370 min—
Thu 29 OctDen Helder Zuid 13:370 min—
Wed 28 OctDen Helder Zuid 13:37No data—
Tue 27 OctDen Helder Zuid 13:360 min—
Mon 26 OctDen Helder Zuid 13:360 min—
Sun 25 OctDen Helder Zuid 13:37No data—
Sat 24 OctDen Helder Zuid 13:360 min—
Fri 23 OctDen Helder Zuid 13:36No data—
Thu 22 OctDen Helder Zuid 13:360 min—
Wed 21 OctDen Helder Zuid 13:36No data—