Train NS 3093 Den Helder – Alkmaar

Den Helder 23:34 → Alkmaar 00:10 Daily 0 h 36 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 23:34 from Den Helder · Fri 6 Nov

Full trip card
Next departure 23:34 today · Den Helder
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 24 full · 2 partial · 2 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 26 full · 3 partial · 14 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: 0 min

Last 30 days

Arrival delay at Alkmaar, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
Den Helder
23:34on time on time
Den Helder Zuid
23:38≈ on time ≈ on time
Anna Paulowna
23:44 / 23:46≈ on time ≈ on time
Schagen
23:52≈ on time ≈ on time
Heerhugowaard
00:02≈ on time ≈ on time
Alkmaar Noord
00:07≈ on time ≈ on time
Alkmaar
00:10on 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
Thu 5 Nov— 00:090 min—
Wed 4 Nov— 00:090 min—
Tue 3 Nov— 00:190 min—
Mon 2 Nov— 00:090 min—
Sun 1 NovAlkmaar Noord 00:190 min—
Sat 31 Oct— 00:110 min—
Thu 29 Oct— 00:110 min+1 min
Wed 28 Oct— 00:110 min—
Tue 27 Oct— 00:120 min—
Mon 26 Oct— 00:110 min—
Sun 25 OctAlkmaar Noord 00:21Partial coverage0 min—
Sat 24 Oct— 00:12No data—
Fri 23 Oct— 00:12+1 min—
Thu 22 Oct— 00:11No data—
Wed 21 Oct— 00:120 min—
Tue 20 Oct— 00:120 min—
Mon 19 Oct— 00:12+1 min+2 min
Sun 18 OctAlkmaar Noord 00:21Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 00:570 min—
Fri 16 Oct— 00:530 min—
Thu 15 Oct— 02:090 min—
Wed 14 Oct— 00:500 min—
Tue 13 Oct— 00:500 min—
Mon 12 Oct— 00:510 min—
Sun 11 OctAlkmaar Noord 00:23+3 min+3 min
Sat 10 Oct— 00:120 min—
Fri 9 Oct— 00:110 min—
Thu 8 Oct— 00:110 min—
Wed 7 Oct— 00:110 min—
Tue 6 Oct— 00:110 min—