Train NS 3080 Nijmegen – Heerhugowaard

Nijmegen 22:13 → Heerhugowaard 00:28 Daily 2 h 15 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 22:13 from Nijmegen · Tue 17 Nov

Next departure 22:13 today · Nijmegen
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 1 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 37 full · 1 partial · 15 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

Worst days

  • Fri 9 Oct Max en route +15 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 37
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
22:13on time on time
22:26 / 22:30≈ on time ≈ on time
22:41≈ on time ≈ on time
22:47≈ on time ≈ on time
23:00≈ on time ≈ on time
23:08 / 23:09≈ on time ≈ on time
23:25≈ on time ≈ on time
23:30≈ on time ≈ on time
23:37 / 23:39≈ on time ≈ on time
23:44≈ on time ≈ on time
23:52≈ on time ≈ on time
00:04≈ on time ≈ on time
00:10≈ on time ≈ on time
00:16 / 00:19≈ on time ≈ on time
00:22≈ on time ≈ on time
00:28on 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
Mon 16 NovAmsterdam Bijlmer ArenA 00:29Partial coverage+1 min—
Sun 15 NovAlkmaar Noord 00:38+2 min+2 min
Sat 14 NovDriebergen-Zeist 00:290 min—
Fri 13 Nov— 22:340 min—
Thu 12 Nov— 00:240 min+5 min
Wed 11 Nov— 00:190 min—
Tue 10 Nov— 00:290 min+5 min
Mon 9 Nov— 00:240 min+2 min
Sun 8 NovDen Helder Zuid 01:190 min—
Sat 7 NovUtrecht Centraal 01:040 min+2 min
Fri 6 Nov— 00:590 min—
Thu 5 Nov— 00:580 min—
Wed 4 Nov— 00:580 min—
Sun 1 NovDen Helder Zuid 01:07+1 min+1 min
Sat 31 OctUtrecht Centraal 01:340 min—
Wed 28 Oct— 01:020 min—
Tue 27 Oct— 00:570 min—
Mon 26 Oct— 00:580 min—
Sun 25 OctDen Helder Zuid 01:060 min—
Sat 24 Oct— 00:580 min—
Fri 23 Oct— 01:260 min+6 min
Thu 22 Oct— 01:40No data—
Wed 21 Oct— 00:570 min—
Tue 20 Oct— 00:570 min—
Mon 19 Oct— 01:240 min—
Sun 18 OctDen Helder Zuid 01:070 min—
Sat 17 OctDen Helder Zuid 01:360 min—
Fri 16 Oct— 00:500 min—
Thu 15 Oct— 01:270 min—
Wed 14 Oct— 01:280 min—