Train NS 3077 Den Helder – Nijmegen

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

Running now · updated 19:36

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 22:17 · 48 km/h

  1. Den Helder19:34
  2. Schagen19:52
  3. Alkmaar20:10
  4. Zaandam20:38
  5. Amsterdam Centraal20:51
  6. Driebergen-Zeist21:32
  7. Nijmegen22:17

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

On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 partial · 31 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 +10 min · last fix heading to Arnhem Centraal +10 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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 10Today
19:34on time on time
19:38≈ on time ≈ on time
19:44 / 19:46≈ on time ≈ on time
19:52≈ on time ≈ on time
20:02≈ on time ≈ on time
20:07≈ on time ≈ on time
20:10 / 20:13≈ on time ≈ on time
20:19≈ on time ≈ on time
20:25≈ on time ≈ on time
20:38≈ on time ≈ on time
20:45≈ on time ≈ on time
20:51 / 20:54≈ on time ≈ on time
21:01 / 21:02≈ on time ≈ +1 min
21:21 / 21:24≈ on time ≈ +1 min
21:32≈ on time ≈ +1 min
21:49≈ on time ≈ +1 min
21:59 / 22:05≈ on time ≈ +1 min
22:17on 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
Fri 6 Nov— 19:340 min—
Thu 5 Nov— 22:330 min—
Wed 4 Nov— 22:190 min—
Tue 3 Nov— 22:190 min—
Mon 2 Nov— 20:290 min—
Sun 1 NovArnhem Centraal 22:19+10 min+10 min
Sat 31 OctVeenendaal-De Klomp 22:010 min—
Fri 30 Oct— 21:520 min—
Thu 29 Oct— 21:58+4 min+4 min
Wed 28 Oct— 21:520 min—
Tue 27 Oct— 21:530 min—
Mon 26 OctAnna Paulowna 21:530 min—
Sun 25 OctDriebergen-Zeist 21:49No data—
Sat 24 OctDriebergen-Zeist 21:50No data—
Fri 23 Oct— 21:010 min—
Thu 22 Oct— 21:34No data—
Wed 21 Oct— 21:34No data—
Tue 20 Oct— 21:340 min—
Mon 19 Oct— 22:190 min—
Sun 18 OctArnhem Centraal 22:190 min—
Sat 17 OctArnhem Centraal 22:21No data—
Fri 16 OctHeerhugowaard 22:180 min—
Thu 15 Oct— 22:20No data—
Wed 14 OctHeerhugowaard 22:40No data—
Tue 13 Oct— 22:190 min—
Mon 12 Oct— 22:180 min—
Sun 11 OctArnhem Centraal 22:190 min—
Sat 10 OctArnhem Centraal 22:190 min—
Fri 9 Oct— 22:180 min—
Thu 8 Oct— 22:19+2 min+2 min