Train NS 2766 Maastricht → Alkmaar

Maastricht 17:27 → Alkmaar 20:29 Sun 3 h 02 min · 13 stops NS (Nederlandse Spoorwegen)

NS 2766 Maastricht–Alkmaar: final delay under 3 min on 4 of its 5 runs with data in the last 30 days (80%). Median final delay: 0 min. Running now, on time. Expected at Alkmaar: 20:29. TrainsRadar data as of 22 Nov 2026, 18:16 (GMT+1).

Running now · updated 18:16

Heading to Alkmaar 0 min

Estimated arrival at Alkmaar 20:29 · 88 km/h

  1. Maastricht17:27
  2. Roermond18:00
  3. Eindhoven Centraal18:31
  4. Utrecht Centraal19:21
  5. Amsterdam Centraal19:50
  6. Zaandam20:06
  7. Alkmaar20:29

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

On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 4 full · 1 partial · 2 no data
On-time · 90 days
71%
5/7 runs under 3 min
RT coverage: 6 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +9 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 15 Nov Max en route +14 min · last fix heading to Castricum +14 min
  • Sun 11 Oct Max en route +9 min · last fix heading to Castricum +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 5
  • 3–10 min 14% · 1
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 7 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
17:27on time on time
17:43 / 17:46≈ on time ≈ +1 min
18:00 / 18:01≈ on time ≈ +2 min
18:15≈ on time ≈ +3 min
18:31 / 18:34≈ on time ≈ +4 min
18:53 / 18:54≈ +1 min ≈ +5 min
19:21 / 19:24≈ +1 min ≈ +6 min
19:42≈ +1 min ≈ +8 min
19:50 / 19:53≈ +1 min ≈ +8 min
19:58≈ +1 min ≈ +8 min
20:06≈ +1 min ≈ +9 min
20:20≈ +1 min ≈ +10 min
20:29+1 min +10 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 22 NovWeert 18:14Partial coverage0 min—
Sun 15 NovCastricum 20:57+14 min+14 min
Sun 8 NovAmsterdam Sloterdijk 20:19+2 min+3 min
Sat 7 NovAmsterdam Sloterdijk 20:190 min—
Sun 1 NovCastricum 20:39No data—
Sun 25 OctCastricum 20:35No data—
Sat 24 OctAmsterdam Sloterdijk 20:240 min—
Sun 18 OctCastricum 20:350 min—
Sun 11 OctCastricum 20:45+7 min+9 min
Sun 4 OctBovenkarspel Flora 21:04No data—
Sun 27 SeptCastricum 20:51No data—
Sun 20 SeptCastricum 20:35No data—
Sun 13 SeptCastricum 20:35No data—
Sun 6 SeptCastricum 20:35No data—
Sun 30 AugCastricum 20:43No data—