Train NS 3067 Den Helder – Nijmegen

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

Running now · updated 18:15

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 19:47 · 48 km/h

  1. Den Helder17:04
  2. Schagen17:22
  3. Alkmaar17:40
  4. Zaandam18:08
  5. Amsterdam Centraal18:21
  6. Driebergen-Zeist19:02
  7. Nijmegen19:47

Today it is running no worse than usual: typical arrival delay is 0 min; 67% of the last 6 runs arrived on time.

On-time · 30 days
67%
4/6 runs under 3 min
RT coverage: 5 full · 1 partial · 24 no data
On-time · 90 days
80%
20/25 runs under 3 min
RT coverage: 24 full · 1 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +13 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

  • Wed 7 Oct Max en route +21 min · last fix heading to Zaandam +21 min
  • Mon 17 Aug Max en route +12 min · last fix heading to Arnhem Centraal +12 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Castricum +5 min
  • Fri 24 Jul Max en route +4 min · last fix heading to Amsterdam Amstel +4 min
  • Sat 25 Jul Max en route +4 min · last fix heading to Amsterdam Centraal +4 min

Distribution · 90 days

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

  • Early 32% · 8
  • On time 48% · 12
  • 3–10 min 12% · 3
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.Today
17:04
17:08
17:14 / 17:16
17:22
17:32
17:37
17:40 / 17:43
17:49
17:55
18:08
18:15
18:21 / 18:24
18:31 / 18:32
18:51 / 18:54
19:02
19:19
19:29 / 19:35
19:47

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.

Recent runs

DateLast stopFinalMax
Sat 10 OctAmsterdam Sloterdijk 18:14Partial coverage0 min—
Fri 9 OctAmsterdam Amstel 19:480 min—
Thu 8 OctCastricum 19:55+5 min+5 min
Wed 7 OctZaandam 19:03+21 min+21 min
Tue 6 OctCastricum 19:480 min—
Mon 5 OctZaandam 19:480 min—
Sun 4 OctArnhem Centraal 19:50No data—
Sat 3 OctArnhem Centraal 19:49No data—
Fri 2 OctAmsterdam Amstel 18:46No data—
Thu 1 OctCastricum 18:10No data—
Wed 30 SeptZaandam 18:18No data—
Tue 29 SeptCastricum 18:09No data—
Mon 28 SeptCastricum 18:09No data—
Sun 27 SeptArnhem Centraal 19:49No data—
Sat 26 SeptArnhem Centraal 19:49No data—
Fri 25 SeptAmsterdam Amstel 18:46No data—
Thu 24 SeptCastricum 18:10No data—
Wed 23 SeptZaandam 18:22No data—
Tue 22 SeptCastricum 18:08No data—
Mon 21 SeptZaandam 18:22No data—
Sun 20 SeptArnhem Centraal 19:51No data—
Sat 19 SeptArnhem Centraal 19:51No data—
Fri 18 SeptAmsterdam Amstel 18:46No data—
Thu 17 SeptZaandam 18:22No data—
Wed 16 SeptCastricum 18:09No data—
Tue 15 SeptZaandam 18:22No data—
Mon 14 SeptZaandam 18:22No data—
Sun 13 SeptArnhem Centraal 19:49No data—
Sat 12 SeptArnhem Centraal 19:49No data—
Fri 11 SeptAmsterdam Amstel 18:43No data—