Train NS 3042 Nijmegen – Heerhugowaard

Nijmegen 12:43 → Heerhugowaard 14:58 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 12:43 from Nijmegen · Thu 19 Nov

Next departure 12:43 today · Nijmegen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 8 no data
On-time · 90 days
95%
60/63 runs under 3 min
RT coverage: 61 full · 2 partial · 25 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: +3 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 17 Nov Max en route +14 min · last fix heading to Alkmaar Noord +14 min
  • Sat 5 Sept Max en route +5 min · last fix heading to Amsterdam Amstel +4 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Alkmaar Noord +3 min

Distribution · 90 days

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

  • Early 21% · 13
  • On time 75% · 47
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 88% T n=8
  • 100% W n=9
  • 100% T n=8
  • 100% F n=8
  • 91% S n=11
  • 90% S n=10

Stops and timetable

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

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