Train NS 3095 Den Helder – Amsterdam Centraal

Den Helder 00:04 → Amsterdam Centraal 01:34 Daily 1 h 30 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:34 0 min

  1. Den Helder00:04
  2. Schagen00:22
  3. Alkmaar Noord00:37
  4. Castricum00:55
  5. Wormerveer01:08
  6. Koog aan de Zaan01:18
  7. Amsterdam Centraal01:34

Next service: tomorrow 00:04 from Den Helder · Sun 8 Nov

Next departure 00:04 tomorrow · Den Helder
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 8 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 Amsterdam Centraal, 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

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

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (17 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 10
00:04on time on time
00:08≈ on time ≈ on time
00:14 / 00:16≈ on time ≈ on time
00:22≈ on time ≈ on time
00:32≈ on time ≈ on time
00:37≈ on time ≈ on time
00:40 / 00:43≈ on time ≈ on time
00:49≈ on time ≈ on time
00:55≈ on time ≈ on time
00:59 / 01:00≈ on time ≈ on time
01:05≈ on time ≈ on time
01:08 / 01:11≈ on time ≈ on time
01:15≈ on time ≈ on time
01:18≈ on time ≈ on time
01:21≈ on time ≈ on time
01:28≈ on time ≈ on time
01:34on 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
Sat 7 Nov— 01:340 min—
Fri 6 Nov— 00:440 min—
Thu 5 Nov— 00:420 min—
Wed 4 Nov— 00:420 min—
Sun 1 NovAlkmaar Noord 00:520 min—
Sat 31 Oct— 01:380 min—
Fri 30 Oct— 00:410 min—
Thu 29 Oct— 00:420 min—
Wed 28 Oct— 00:420 min—
Tue 27 Oct— 00:440 min—
Sun 25 OctAlkmaar Noord 00:510 min—
Sat 24 Oct— 01:360 min—
Fri 23 Oct— 00:420 min—
Thu 22 Oct— 00:410 min—
Tue 20 Oct— 00:450 min—
Sun 18 OctAlkmaar Noord 00:510 min—
Sat 17 Oct— 01:220 min—
Thu 15 Oct— 00:140 min—
Wed 14 Oct— 00:110 min—
Tue 13 Oct— 00:120 min—
Sun 11 OctAlkmaar Noord 00:510 min—
Sat 10 Oct— 01:37+1 min+1 min
Fri 9 Oct— 00:410 min—
Thu 8 Oct— 00:42+1 min—
Wed 7 Oct— 00:410 min—
Tue 6 OctDen Helder Zuid 00:410 min—
Sun 4 OctAlkmaar Noord 00:51No data—
Sun 27 SeptAlkmaar Noord 00:51No data—
Sun 20 SeptAlkmaar Noord 00:51No data—
Sun 13 SeptAlkmaar Noord 00:51No data—