Train NS 3076 Nijmegen – Den Helder

Nijmegen 21:13 → Den Helder 23:56 Daily 2 h 43 min · 18 stops NS (Nederlandse Spoorwegen)

Running now · updated 21:22

Heading to Den Helder 0 min

Estimated arrival at Den Helder 23:56 · 131 km/h

  1. Nijmegen21:13
  2. Driebergen-Zeist21:58
  3. Amsterdam Centraal22:35
  4. Castricum23:04
  5. Alkmaar23:16
  6. Schagen23:37
  7. Den Helder23:56

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

Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 5 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 27 full · 1 partial · 21 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: +1 min

Last 30 days

Arrival delay at Den Helder, 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 23 Oct Max en route +30 min · last fix heading to — +30 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
Nijmegen
21:13on time on time
Arnhem Centraal
21:26 / 21:31≈ on time ≈ on time
Ede-Wageningen
21:41≈ on time ≈ on time
Driebergen-Zeist
21:58≈ on time ≈ on time
Utrecht Centraal
22:06 / 22:09≈ on time ≈ on time
Amsterdam Amstel
22:28≈ on time ≈ on time
Amsterdam Centraal
22:35 / 22:39≈ on time ≈ on time
Amsterdam Sloterdijk
22:44≈ on time ≈ on time
Zaandam
22:52≈ on time ≈ on time
Castricum
23:04≈ on time ≈ on time
Heiloo
23:10≈ on time ≈ +1 min
Alkmaar
23:16 / 23:19≈ on time ≈ +1 min
Alkmaar Noord
23:22≈ on time ≈ +1 min
Heerhugowaard
23:27≈ on time ≈ +1 min
Schagen
23:37≈ on time ≈ +1 min
Anna Paulowna
23:43 / 23:45≈ on time ≈ +1 min
Den Helder Zuid
23:52≈ on time ≈ +1 min
Den Helder
23:56on 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
Sat 7 NovNijmegen 21:19Partial coverage0 min—
Fri 6 Nov— 23:58+1 min+3 min
Thu 5 Nov— 23:570 min—
Wed 4 Nov— 23:58+1 min+2 min
Tue 3 Nov— 23:58No data—
Mon 2 Nov— 23:570 min—
Sun 1 NovDen Helder Zuid 00:040 min+7 min
Sat 31 OctAlkmaar Noord 00:300 min—
Thu 29 Oct— 00:000 min+1 min
Wed 28 Oct— 23:580 min—
Tue 27 Oct— 23:200 min—
Mon 26 Oct— 23:230 min—
Sun 25 OctDen Helder Zuid 00:060 min—
Sat 24 OctAmsterdam Centraal 00:000 min—
Fri 23 Oct— 22:25+30 min+30 min
Thu 22 Oct— 23:57No data—
Wed 21 Oct— 23:58No data—
Tue 20 Oct— 23:570 min—
Mon 19 Oct— 00:000 min+2 min
Sun 18 OctDen Helder Zuid 00:060 min—
Sat 17 OctDen Helder Zuid 00:370 min—
Fri 16 Oct— 23:470 min+2 min
Thu 15 Oct— 00:27No data—
Wed 14 Oct— 00:270 min—
Tue 13 Oct— 00:27No data—
Mon 12 Oct— 00:270 min—
Sun 11 OctDen Helder Zuid 00:08+1 min+3 min
Sat 10 OctDriebergen-Zeist 23:580 min—
Fri 9 Oct— 23:570 min—
Thu 8 Oct— 23:58+1 min—