Train NS 3048 Nijmegen – Den Helder

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 14:13 from Nijmegen · Thu 5 Nov

Next departure 14:13 today · Nijmegen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
95%
41/43 runs under 3 min
RT coverage: 38 full · 5 partial · 45 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: +1 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

  • Sat 10 Oct Max en route +17 min · last fix heading to Den Helder Zuid +15 min
  • Sat 26 Sept Max en route +7 min · last fix heading to Den Helder Zuid +7 min

Distribution · 90 days

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

  • Early 30% · 13
  • On time 65% · 28
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=6
  • 100% T n=8
  • 100% F n=7
  • 60% S n=5
  • 100% S n=6

Stops and timetable

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

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