Train NS 3082 Nijmegen – Den Helder

Nijmegen 22:43 → Den Helder 01:26 Daily 2 h 43 min · 20 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:43 from Nijmegen · Fri 6 Nov

Next departure 22:43 today · Nijmegen
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 19 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 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

  • Mon 2 Nov Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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:43on time on time
22:56 / 23:00≈ on time ≈ on time
23:10≈ on time ≈ on time
23:16≈ on time ≈ on time
23:29≈ on time ≈ on time
23:37 / 23:39≈ on time ≈ on time
23:55≈ on time ≈ on time
00:00≈ on time ≈ on time
00:07 / 00:09≈ on time ≈ on time
00:14≈ on time ≈ on time
00:22≈ on time ≈ on time
00:34≈ on time ≈ on time
00:40≈ on time ≈ on time
00:46 / 00:49≈ on time ≈ on time
00:52≈ on time ≈ on time
00:57≈ on time ≈ on time
01:07≈ on time ≈ on time
01:13 / 01:15≈ on time ≈ on time
01:22≈ on time ≈ on time
01:26on 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
Thu 5 Nov— 00:080 min—
Wed 4 Nov— 01:290 min—
Tue 3 Nov— 00:540 min—
Mon 2 Nov— 01:04+8 min+9 min
Sun 1 NovDen Helder Zuid 01:380 min+6 min
Sat 31 OctVeenendaal-De Klomp 01:270 min—
Fri 30 Oct— 03:020 min—
Thu 29 Oct— 01:27+1 min—
Wed 28 Oct— 01:270 min—
Tue 27 Oct— 00:500 min—
Mon 26 Oct— 00:500 min—
Sun 25 OctDen Helder Zuid 01:36No data—
Sat 24 Oct— 01:280 min—
Fri 23 Oct— 01:280 min—
Thu 22 Oct— 01:27No data—
Wed 21 Oct— 01:270 min—
Tue 20 Oct— 00:550 min—
Mon 19 Oct— 00:560 min—
Sun 18 OctDen Helder Zuid 01:430 min+4 min
Sat 17 OctHeerhugowaard 01:57No data—
Fri 16 Oct— 01:20+2 min+5 min
Thu 15 Oct— 01:180 min—
Wed 14 Oct— 01:570 min—
Tue 13 Oct— 00:080 min—
Mon 12 Oct— 01:190 min—
Sun 11 OctDen Helder Zuid 01:360 min—
Sat 10 Oct— 01:380 min—
Fri 9 Oct— 01:410 min+4 min
Thu 8 Oct— 01:270 min—
Wed 7 Oct— 01:470 min+5 min