Train NS 3087 Heerhugowaard – Nijmegen

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

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 22:32 from Heerhugowaard · Sun 15 Nov

Next departure 22:32 today · Heerhugowaard
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 27 full · 1 partial · 1 no data
On-time · 90 days
97%
38/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 Nijmegen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +18 min · last fix heading to Arnhem Centraal +18 min

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 97% · 38
  • 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=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=6
  • 75% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (16 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
22:32on time on time
22:37≈ on time ≈ on time
22:40 / 22:43≈ on time ≈ on time
22:49≈ on time ≈ on time
22:55≈ on time ≈ on time
23:08≈ on time ≈ on time
23:15≈ on time ≈ on time
23:21 / 23:23≈ on time ≈ on time
23:31≈ on time ≈ on time
23:36≈ on time ≈ on time
23:52 / 23:53≈ on time ≈ on time
00:01≈ on time ≈ on time
00:14≈ on time ≈ on time
00:20≈ on time ≈ on time
00:30 / 00:35≈ on time ≈ on time
00:47on 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
Sat 14 NovCastricum 00:48Partial coverage0 min—
Fri 13 Nov— 00:480 min—
Thu 12 Nov— 01:070 min—
Wed 11 Nov— 00:490 min—
Tue 10 Nov— 00:480 min—
Mon 9 Nov— 00:480 min—
Sun 8 NovArnhem Centraal 00:490 min—
Sat 7 NovAmsterdam Sloterdijk 00:540 min—
Fri 6 Nov— 00:590 min+3 min
Thu 5 Nov— 01:070 min—
Wed 4 Nov— 00:540 min+3 min
Tue 3 Nov— 00:490 min—
Mon 2 Nov— 00:540 min—
Sun 1 NovArnhem Centraal 01:19+18 min+18 min
Sat 31 OctAmsterdam Sloterdijk 00:390 min—
Fri 30 Oct— 00:360 min—
Thu 29 Oct— 00:290 min+5 min
Wed 28 Oct— 00:220 min—
Tue 27 Oct— 00:270 min—
Mon 26 Oct— 00:220 min—
Sun 25 OctVeenendaal-De Klomp 00:33No data—
Sat 24 OctHeerhugowaard 00:270 min—
Fri 23 Oct— 00:030 min+6 min
Thu 22 Oct— 00:090 min—
Wed 21 Oct— 00:090 min—
Tue 20 Oct— 00:070 min—
Mon 19 Oct— 00:490 min—
Sun 18 OctArnhem Centraal 00:500 min—
Sat 17 OctArnhem Centraal 00:590 min—
Fri 16 Oct— 00:550 min—