Train NS 3078 Nijmegen – Heerhugowaard

Nijmegen 21:43 → Heerhugowaard 23:58 Daily 2 h 15 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 21:43 from Nijmegen · Tue 17 Nov

Next departure 21:43 today · Nijmegen
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 24 full · 1 partial · 2 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 38 full · 1 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
21:43on time on time
21:56 / 22:00≈ on time ≈ on time
22:10≈ on time ≈ on time
22:16≈ on time ≈ on time
22:29≈ on time ≈ on time
22:37 / 22:39≈ on time ≈ on time
22:57≈ on time ≈ on time
23:05 / 23:09≈ on time ≈ on time
23:14≈ on time ≈ on time
23:22≈ on time ≈ on time
23:35≈ on time ≈ on time
23:41≈ on time ≈ on time
23:46 / 23:49≈ on time ≈ on time
23:53≈ on time ≈ on time
23:58on time on time

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
Sun 15 NovAlkmaar Noord 00:07Partial coverage0 min—
Sat 14 NovAmsterdam Amstel 23:590 min—
Fri 13 Nov— 00:040 min+7 min
Thu 12 Nov— 23:490 min+2 min
Wed 11 Nov— 23:58+2 min+4 min
Tue 10 Nov— 23:130 min—
Mon 9 Nov— 23:490 min+1 min
Sun 8 NovDen Helder Zuid 00:380 min—
Sat 7 NovZaandam 00:280 min—
Fri 6 Nov— 00:29+2 min+2 min
Thu 5 Nov— 21:580 min—
Wed 4 Nov— 00:280 min+2 min
Mon 2 Nov— 00:27+1 min—
Sun 1 NovDen Helder Zuid 00:340 min+4 min
Sat 31 OctZaandam 00:270 min—
Fri 30 Oct— 00:270 min—
Thu 29 Oct— 00:270 min—
Wed 28 Oct— 00:27No data—
Tue 27 Oct— 00:280 min—
Mon 26 Oct— 00:280 min—
Sun 25 OctDen Helder Zuid 00:370 min—
Sat 24 OctUtrecht Centraal 00:270 min—
Fri 23 Oct— 00:280 min—
Thu 22 Oct— 00:300 min—
Wed 21 Oct— 00:270 min—
Tue 20 Oct— 23:50No data—
Mon 19 Oct— 00:300 min—
Sun 18 OctDen Helder Zuid 00:370 min—
Sat 17 OctDen Helder Zuid 01:050 min—
Fri 16 Oct— 00:180 min—