Train NS 3085 Den Helder – Nijmegen

Den Helder 21:34 → Nijmegen 00:17 Daily 2 h 43 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

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

Next departure 21:34 today · Den Helder
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 24 full · 1 partial · 3 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 20 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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 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 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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 10
21:34on time on time
21:38≈ on time ≈ on time
21:44 / 21:46≈ on time ≈ on time
21:52≈ on time ≈ on time
22:02≈ on time ≈ on time
22:07≈ on time ≈ on time
22:10 / 22:13≈ on time ≈ on time
22:19≈ on time ≈ on time
22:25≈ on time ≈ on time
22:38≈ on time ≈ on time
22:45≈ on time ≈ on time
22:51 / 22:54≈ on time ≈ on time
23:01 / 23:02≈ on time ≈ on time
23:21 / 23:23≈ on time ≈ on time
23:31≈ on time ≈ on time
23:44≈ on time ≈ on time
23:50≈ on time ≈ on time
00:00 / 00:05≈ on time ≈ on time
00:17on 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:190 min—
Wed 4 Nov— 00:390 min+8 min
Tue 3 Nov— 00:290 min—
Sun 1 NovArnhem Centraal 00:29Partial coverage0 min+10 min
Sat 31 OctAmsterdam Bijlmer ArenA 23:520 min—
Fri 30 Oct— 23:530 min—
Thu 29 Oct— 22:110 min—
Wed 28 Oct— 22:31No data—
Tue 27 Oct— 23:53No data—
Mon 26 Oct— 23:520 min—
Sun 25 OctVeenendaal-De Klomp 00:000 min—
Sat 24 OctZaandam 00:000 min—
Fri 23 Oct— 23:33+5 min+5 min
Thu 22 Oct— 23:360 min—
Wed 21 Oct— 23:320 min—
Tue 20 Oct— 23:35No data—
Mon 19 Oct— 00:180 min—
Sun 18 OctArnhem Centraal 00:200 min—
Sat 17 OctArnhem Centraal 00:190 min—
Fri 16 Oct— 00:140 min—
Thu 15 Oct— 00:220 min—
Wed 14 Oct— 00:180 min—
Tue 13 Oct— 00:190 min—
Mon 12 Oct— 00:180 min—
Sun 11 OctArnhem Centraal 00:190 min—
Sat 10 OctHeerhugowaard 00:190 min—
Fri 9 Oct— 00:33+8 min+8 min
Thu 8 Oct— 00:170 min—
Wed 7 Oct— 00:220 min—
Tue 6 Oct— 00:180 min—