Train NS 3032 Nijmegen – Heerhugowaard

Nijmegen 10:13 → Heerhugowaard 12: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 10:13 from Nijmegen · Thu 19 Nov

Next departure 10:13 today · Nijmegen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 19 full · 3 partial · 7 no data
On-time · 90 days
97%
66/68 runs under 3 min
RT coverage: 65 full · 3 partial · 20 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 8 Sept Max en route +14 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Alkmaar Noord +3 min

Distribution · 90 days

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

  • Early 25% · 17
  • On time 72% · 49
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 89% T n=9
  • 100% W n=10
  • 100% T n=9
  • 100% F n=9
  • 100% S n=10
  • 89% S n=9

Stops and timetable

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

Last 90 days, 68 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:13on time on time
10:26 / 10:31≈ on time ≈ on time
10:41≈ on time ≈ on time
10:58≈ on time ≈ on time
11:06 / 11:09≈ on time ≈ on time
11:28≈ on time ≈ on time
11:35 / 11:39≈ on time ≈ +1 min
11:44≈ on time ≈ +1 min
11:52≈ on time ≈ +1 min
12:04≈ on time ≈ +1 min
12:10≈ on time ≈ +1 min
12:16 / 12:19≈ on time ≈ +1 min
12:22≈ on time ≈ +1 min
12:28on 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 12:34Partial coverage0 min—
Tue 17 NovAlkmaar Noord 12:38Partial coverage+1 min+1 min
Mon 16 NovAlkmaar Noord 12:38Partial coverage0 min—
Sun 15 NovAlkmaar Noord 12:40+3 min+4 min
Sat 14 NovAlkmaar Noord 12:37+1 min+1 min
Fri 13 NovHeiloo 12:27+1 min—
Thu 12 NovHeiloo 12:240 min—
Wed 11 NovHeiloo 12:240 min—
Tue 10 NovHeiloo 12:24+1 min+2 min
Mon 9 NovHeiloo 12:24+1 min—
Sun 8 NovDen Helder Zuid 13:04+1 min+3 min
Sat 7 NovDen Helder Zuid 13:040 min—
Fri 6 NovDen Helder Zuid 13:12No data—
Thu 5 NovDen Helder Zuid 13:04No data—
Wed 4 NovDen Helder Zuid 13:040 min—
Tue 3 NovDen Helder Zuid 13:07No data—
Mon 2 NovDen Helder Zuid 13:04No data—
Sun 1 NovCastricum 12:48+2 min+2 min
Sat 31 OctDen Helder Zuid 13:07+1 min+3 min
Fri 30 OctDen Helder Zuid 13:09No data—
Thu 29 OctDen Helder Zuid 13:060 min—
Wed 28 OctDen Helder Zuid 13:060 min—
Tue 27 OctDen Helder Zuid 13:060 min—
Mon 26 OctDen Helder Zuid 13:060 min—
Sun 25 OctDen Helder Zuid 13:06No data—
Sat 24 OctDen Helder Zuid 13:08+2 min+7 min
Fri 23 OctDen Helder Zuid 13:060 min—
Thu 22 OctDen Helder Zuid 13:06No data—
Wed 21 OctDen Helder Zuid 13:060 min—
Tue 20 OctDen Helder Zuid 13:060 min—