Train NS 2771 Heerhugowaard – Alkmaar

Heerhugowaard 18:16 → Alkmaar 18:24 Daily 0 h 08 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 18:16 from Heerhugowaard · Wed 18 Nov

Next departure 18:16 today · Heerhugowaard
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 8 full · 1 partial · 1 no data
On-time · 90 days
77%
10/13 runs under 3 min
RT coverage: 12 full · 1 partial · 13 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +6 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

Worst days

  • Sun 18 Oct Max en route +13 min · last fix heading to Sittard +10 min
  • Sun 15 Nov Max en route +8 min · last fix heading to Weert +8 min
  • Sat 14 Nov Max en route +6 min · last fix heading to Weert +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 10
  • 3–10 min 15% · 2
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
18:16on time on time
18:21≈ +1 min ≈ +5 min
18:24+1 min +8 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
Tue 17 NovAlkmaar Noord 18:34Partial coverage0 min—
Mon 16 NovAlkmaar Noord 18:350 min—
Sun 15 NovWeert 21:18+8 min+8 min
Sat 14 NovWeert 21:14+6 min+6 min
Sun 8 NovSittard 21:33+1 min+1 min
Sat 7 NovEindhoven Centraal 21:33+3 min+3 min
Sun 1 NovAmsterdam Amstel 19:39+2 min+2 min
Sat 31 OctSittard 21:390 min—
Sun 25 OctSittard 21:37No data—
Sat 24 OctSittard 21:380 min—
Sun 18 OctSittard 21:55+10 min+13 min
Sat 17 OctSittard 21:350 min—
Sun 11 OctEde-Wageningen 20:210 min—
Sat 10 OctSittard 21:37+2 min+4 min
Sun 4 OctSittard 21:36No data—
Sat 3 OctSittard 22:03No data—
Sun 27 SeptSittard 21:41No data—
Sat 26 SeptSittard 21:33No data—
Sun 20 SeptUtrecht Centraal 19:53No data—
Sat 19 SeptUtrecht Centraal 19:53No data—
Sun 13 SeptSittard 21:32No data—
Sat 12 SeptSittard 22:00No data—
Sun 6 SeptWeert 21:03No data—
Sat 5 SeptWeert 21:02No data—
Sun 30 AugSittard 21:36No data—
Sat 29 AugSittard 21:32No data—