Train NS 3088 Amsterdam Centraal – Heerhugowaard

Amsterdam Centraal 01:49 → Heerhugowaard 02:47 Fri, Sat 0 h 58 min · 13 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November +3 min

Next service: Friday 01:49 from Amsterdam Centraal · Fri 20 Nov

Next departure 01:49 Friday · Amsterdam Centraal
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 1 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Heerhugowaard, 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 14 Nov Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 83% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 15 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
01:49on time on time
01:55≈ on time ≈ on time
02:02≈ on time ≈ on time
02:06≈ on time ≈ +1 min
02:08≈ on time ≈ +1 min
02:12≈ on time ≈ +1 min
02:16≈ on time ≈ +1 min
02:22≈ on time ≈ +1 min
02:27≈ on time ≈ +1 min
02:32≈ on time ≈ +2 min
02:38 / 02:39≈ on time ≈ +2 min
02:42≈ on time ≈ +2 min
02:47on time +2 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
Sun 15 Nov— 02:54+3 min+3 min
Sat 14 Nov— 02:48+3 min+4 min
Sun 8 Nov— 02:48+1 min—
Sat 7 Nov— 02:490 min—
Sun 1 Nov— 02:510 min—
Sat 31 Oct— 02:510 min—
Mon 26 OctDriebergen-Zeist 01:13No data—
Sun 25 Oct— 02:500 min—
Sat 24 Oct— 03:080 min—
Fri 23 Oct— 01:090 min—
Thu 22 Oct— 01:070 min—
Wed 21 Oct— 01:080 min—
Sun 18 Oct— 02:570 min—
Sat 17 Oct— 03:180 min—
Sun 11 Oct— 02:51+1 min—
Sat 10 Oct— 02:510 min+1 min