Train NS 3040 Nijmegen – Den Helder

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

✓ Today’s run finished

Today, last fix heading to Den Helder Zuid at 15:04 No data

  1. Nijmegen12:13
  2. Driebergen-Zeist12:58
  3. Amsterdam Centraal13:35
  4. Castricum14:04
  5. Alkmaar14:16
  6. Den Helder Zuid14:52
  7. Den Helder14:56

Next service: tomorrow 12:13 from Nijmegen · Sat 7 Nov

Next departure 12:13 tomorrow · Nijmegen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 16 full · 3 partial · 11 no data
On-time · 90 days
98%
51/52 runs under 3 min
RT coverage: 48 full · 4 partial · 37 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: +2 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 9 Oct Max en route +7 min · last fix heading to Den Helder Zuid +6 min

Distribution · 90 days

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

  • Early 17% · 9
  • On time 81% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=9
  • 100% T n=7
  • 86% F n=7
  • 100% S n=10
  • 100% S n=7

Stops and timetable

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

Last 90 days, 52 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
12:13on time on time
12:26 / 12:31≈ on time ≈ on time
12:41≈ on time ≈ on time
12:58≈ on time ≈ on time
13:06 / 13:09≈ on time ≈ +1 min
13:28≈ on time ≈ +1 min
13:35 / 13:39≈ on time ≈ +1 min
13:44≈ on time ≈ +1 min
13:52≈ on time ≈ +1 min
14:04≈ on time ≈ +1 min
14:10≈ on time ≈ +1 min
14:16 / 14:19≈ on time ≈ +1 min
14:22≈ on time ≈ +1 min
14:27≈ on time ≈ +1 min
14:37≈ on time ≈ +1 min
14:43 / 14:45≈ on time ≈ +1 min
14:52≈ on time ≈ +2 min
14:56on 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
Fri 6 NovDen Helder Zuid 15:04No data—
Thu 5 NovDen Helder Zuid 15:04No data—
Wed 4 NovDen Helder Zuid 15:04Partial coverage0 min—
Tue 3 NovDen Helder Zuid 15:04No data—
Mon 2 NovDen Helder Zuid 15:04No data—
Sun 1 NovBunnik 13:27+2 min+2 min
Sat 31 OctDen Helder Zuid 15:08+2 min+2 min
Fri 30 OctDen Helder Zuid 15:06No data—
Thu 29 OctDen Helder Zuid 15:06No data—
Wed 28 OctDen Helder Zuid 15:06No data—
Tue 27 OctDen Helder Zuid 15:070 min—
Mon 26 OctDen Helder Zuid 15:06No data—
Sun 25 OctDen Helder Zuid 15:08No data—
Sat 24 OctDen Helder Zuid 15:060 min—
Fri 23 OctDen Helder Zuid 15:06No data—
Thu 22 OctDen Helder Zuid 15:070 min—
Wed 21 OctDen Helder Zuid 15:260 min—
Tue 20 OctDen Helder Zuid 15:06No data—
Mon 19 OctDen Helder Zuid 15:07Partial coverage0 min—
Sun 18 OctDen Helder Zuid 15:060 min—
Sat 17 OctDen Helder Zuid 15:360 min—
Fri 16 OctAlkmaar Noord 14:570 min—
Thu 15 OctDen Helder Zuid 15:360 min—
Wed 14 OctDen Helder Zuid 15:360 min—
Tue 13 OctDen Helder Zuid 15:360 min—
Mon 12 OctDen Helder Zuid 15:360 min—
Sun 11 OctDen Helder Zuid 15:060 min—
Sat 10 OctDen Helder Zuid 15:060 min—
Fri 9 OctDen Helder Zuid 15:12+6 min+7 min
Thu 8 OctDen Helder Zuid 15:06Partial coverage0 min—