Train NS 3068 Nijmegen – Heerhugowaard

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

Running now · updated 20:05

Heading to Heerhugowaard 0 min

Estimated arrival at Heerhugowaard 21:28 · 141 km/h

  1. Nijmegen19:13
  2. Ede-Wageningen19:41
  3. Utrecht Centraal20:06
  4. Amsterdam Sloterdijk20:44
  5. Castricum21:04
  6. Alkmaar21:16
  7. Heerhugowaard21:28

Today it is running no worse than usual: typical arrival delay is 0 min; 83% of the last 24 runs arrived on time.

On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
91%
48/53 runs under 3 min
RT coverage: 53 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +10 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 +21 min · last fix heading to — +20 min
  • Fri 6 Nov Max en route +17 min · last fix heading to — +15 min
  • Wed 7 Oct Max en route +15 min · last fix heading to — +15 min
  • Wed 4 Nov Max en route +15 min · last fix heading to — +13 min
  • Wed 18 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 9% · 5
  • On time 81% · 43
  • 3–10 min 2% · 1
  • 10–30 min 8% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 83% T n=6
  • 40% W n=5
  • 100% T n=6
  • 80% F n=5
  • 100% S n=11
  • 100% S n=11

Stops and timetable

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

Last 90 days, 53 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 10Today
19:13on time on time
19:26 / 19:31≈ on time ≈ on time
19:41≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:06 / 20:09≈ on time ≈ +1 min
20:28≈ on time ≈ +2 min
20:35 / 20:39≈ on time ≈ +2 min
20:44≈ on time ≈ +2 min
20:52≈ on time ≈ +2 min
21:04≈ on time ≈ +2 min
21:10≈ on time ≈ +3 min
21:16 / 21:19≈ on time ≈ +3 min
21:22≈ on time ≈ +3 min
21:28on time +3 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 Nov— 20:040 min—
Wed 18 Nov— 21:34+3 min+3 min
Tue 17 Nov— 21:59+20 min+21 min
Mon 16 Nov— 19:28+3 min+3 min
Sun 15 NovAlkmaar Noord 21:38+2 min+2 min
Sat 14 NovAlkmaar Noord 21:370 min+1 min
Fri 13 Nov— 21:230 min+4 min
Thu 12 Nov— 21:23+1 min+1 min
Wed 11 Nov— 21:19+1 min+1 min
Tue 10 Nov— 21:19+1 min—
Mon 9 Nov— 21:190 min—
Sun 8 NovDen Helder Zuid 22:040 min—
Sat 7 NovDen Helder Zuid 22:040 min—
Fri 6 Nov— 22:28+15 min+17 min
Thu 5 Nov— 21:59No data—
Wed 4 Nov— 22:22+13 min+15 min
Tue 3 Nov— 21:590 min—
Mon 2 Nov— 20:480 min—
Sun 1 NovDen Helder Zuid 22:19+1 min+1 min
Sat 31 OctDen Helder Zuid 22:060 min—
Thu 29 Oct— 21:570 min—
Wed 28 Oct— 21:59No data—
Tue 27 Oct— 21:580 min—
Mon 26 OctEde-Wageningen 21:57No data—
Sun 25 OctDen Helder Zuid 22:07No data—
Sat 24 OctDen Helder Zuid 22:070 min—
Fri 23 Oct— 21:570 min—
Thu 22 Oct— 21:580 min—
Wed 21 Oct— 21:58No data—
Tue 20 Oct— 22:06No data—