Train NS 3063 Den Helder – Nijmegen

Den Helder 16:04 → Nijmegen 18:47 Daily 2 h 43 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 16:04 from Den Helder · Sun 8 Nov

Next departure 16:04 today · Den Helder
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 15 full · 7 partial · 7 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 38 full · 10 partial · 40 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 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 +20 min · last fix heading to Arnhem Centraal +20 min
  • Wed 7 Oct Max en route +18 min · last fix heading to Driebergen-Zeist +18 min

Distribution · 90 days

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

  • Early 31% · 15
  • On time 65% · 31
  • 3–10 min 0% · 0
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 86% W n=7
  • 100% T n=7
  • 100% F n=9
  • 100% S n=8
  • 80% S n=5

Stops and timetable

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

Last 90 days, 48 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
16:04on time on time
16:08≈ on time ≈ on time
16:14 / 16:16≈ on time ≈ on time
16:22≈ on time ≈ on time
16:32≈ on time ≈ on time
16:37≈ on time ≈ on time
16:40 / 16:43≈ on time ≈ on time
16:49≈ on time ≈ on time
16:55≈ on time ≈ on time
17:08≈ on time ≈ on time
17:15≈ on time ≈ on time
17:21 / 17:24≈ on time ≈ on time
17:31 / 17:32≈ on time ≈ on time
17:51 / 17:54≈ on time ≈ on time
18:02≈ on time ≈ on time
18:19≈ on time ≈ +1 min
18:29 / 18:35≈ on time ≈ +1 min
18:47on 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 NovArnhem Centraal 18:49Partial coverage0 min—
Fri 6 NovArnhem Centraal 18:49Partial coverage+1 min+1 min
Thu 5 NovDriebergen-Zeist 19:04Partial coverage0 min—
Wed 4 NovDriebergen-Zeist 18:490 min—
Tue 3 NovDriebergen-Zeist 18:48Partial coverage0 min—
Mon 2 NovDriebergen-Zeist 18:48Partial coverage+1 min+1 min
Sun 1 NovArnhem Centraal 18:49+20 min+20 min
Sat 31 OctVeenendaal-De Klomp 18:32+1 min+3 min
Fri 30 OctVeenendaal-De Klomp 18:290 min—
Thu 29 OctDriebergen-Zeist 18:30No data—
Wed 28 OctDriebergen-Zeist 18:220 min—
Tue 27 OctDriebergen-Zeist 18:290 min—
Mon 26 OctDriebergen-Zeist 18:220 min—
Sun 25 OctDriebergen-Zeist 18:20No data—
Sat 24 OctDriebergen-Zeist 18:200 min—
Fri 23 OctUtrecht Centraal 18:08No data—
Thu 22 OctUtrecht Centraal 18:100 min—
Wed 21 OctUtrecht Centraal 18:080 min—
Tue 20 OctUtrecht Centraal 18:080 min—
Mon 19 OctArnhem Centraal 18:49No data—
Sun 18 OctArnhem Centraal 18:56Partial coverage0 min—
Sat 17 OctArnhem Centraal 18:490 min—
Fri 16 OctArnhem Centraal 18:490 min—
Thu 15 OctEde-Wageningen 18:50No data—
Wed 14 OctArnhem Centraal 18:49No data—
Tue 13 OctArnhem Centraal 18:49No data—
Mon 12 OctArnhem Centraal 18:490 min—
Sun 11 OctArnhem Centraal 18:490 min—
Sat 10 OctArnhem Centraal 18:52Partial coverage+3 min+3 min
Fri 9 OctArnhem Centraal 18:49Partial coverage+2 min+2 min