Train NS 3081 Den Helder – Nijmegen

Den Helder 20:34 → Nijmegen 23:17 Daily 2 h 43 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 20:34 from Den Helder · Fri 6 Nov

Next departure 20:34 today · Den Helder
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 6 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 +13 min · last fix heading to Arnhem Centraal +13 min
  • Wed 4 Nov Max en route +12 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 0% · 0
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
20:34on time on time
20:38≈ on time ≈ on time
20:44 / 20:46≈ on time ≈ on time
20:52≈ on time ≈ on time
21:02≈ on time ≈ on time
21:07≈ on time ≈ on time
21:10 / 21:13≈ on time ≈ on time
21:19≈ on time ≈ on time
21:25≈ on time ≈ +1 min
21:38≈ on time ≈ +1 min
21:45≈ on time ≈ +1 min
21:51 / 21:54≈ on time ≈ +1 min
22:01 / 22:02≈ on time ≈ +1 min
22:21 / 22:24≈ on time ≈ +1 min
22:32≈ on time ≈ +1 min
22:49≈ on time ≈ +1 min
22:59 / 23:05≈ on time ≈ +2 min
23:17on time +2 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
Thu 5 Nov— 23:180 min—
Wed 4 Nov— 23:39+11 min+12 min
Tue 3 Nov— 23:19No data—
Mon 2 Nov— 22:390 min—
Sun 1 NovArnhem Centraal 23:19+13 min+13 min
Sat 31 OctVeenendaal-De Klomp 22:590 min—
Thu 29 Oct— 22:57+2 min+3 min
Wed 28 Oct— 22:55No data—
Tue 27 Oct— 23:030 min—
Mon 26 Oct— 22:53No data—
Sun 25 OctDriebergen-Zeist 22:51No data—
Sat 24 OctDriebergen-Zeist 22:590 min—
Fri 23 Oct— 22:26+1 min+1 min
Thu 22 Oct— 22:340 min—
Wed 21 Oct— 22:480 min—
Tue 20 Oct— 22:42No data—
Mon 19 Oct— 23:400 min—
Sun 18 OctArnhem Centraal 23:190 min—
Sat 17 OctArnhem Centraal 23:200 min—
Fri 16 Oct— 23:180 min—
Thu 15 Oct— 23:23No data—
Wed 14 Oct— 23:180 min—
Tue 13 Oct— 23:190 min—
Mon 12 Oct— 23:180 min—
Sun 11 OctArnhem Centraal 23:190 min—
Sat 10 OctAmsterdam Amstel 23:190 min—
Fri 9 Oct— 23:18+1 min+1 min
Wed 7 Oct— 23:18+2 min+2 min
Tue 6 Oct— 23:180 min—
Mon 5 Oct— 23:180 min—