Train NS 2722 Maastricht – Alkmaar

Maastricht 06:31 → Alkmaar 09:33 Mon, Tue, Wed, Thu, Fri, Sat 3 h 02 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Centraal at 09:49 0 min

  1. Maastricht06:31
  2. Roermond07:01
  3. Eindhoven Centraal07:33
  4. Utrecht Centraal08:27
  5. Amsterdam Centraal08:55
  6. Amsterdam Sloterdijk09:03
  7. Alkmaar09:33

Next service: tomorrow 06:31 from Maastricht · Fri 6 Nov

Next departure 06:31 tomorrow · Maastricht
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 16 full · 6 partial · 1 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 16 full · 7 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 9 Oct Max en route +12 min · last fix heading to Castricum +12 min
  • Tue 3 Nov Max en route +9 min · last fix heading to Castricum +9 min
  • Wed 4 Nov Max en route +6 min · last fix heading to Castricum +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 9% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 80% W n=5
  • 100% T n=5
  • 75% F n=4
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
06:31on time on time
06:46 / 06:47≈ on time ≈ on time
07:01 / 07:02≈ on time ≈ +1 min
07:16≈ on time ≈ +1 min
07:33 / 07:36≈ on time ≈ +1 min
07:56 / 08:00≈ on time ≈ +2 min
08:27 / 08:29≈ on time ≈ +2 min
08:47≈ on time ≈ +3 min
08:55 / 08:58≈ on time ≈ +3 min
09:03 / 09:05≈ on time ≈ +3 min
09:12≈ on time ≈ +3 min
09:24≈ on time ≈ +3 min
09:33on time +3 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
Thu 5 NovAmsterdam Centraal 09:49Partial coverage0 min—
Wed 4 NovCastricum 09:44+6 min+6 min
Tue 3 NovCastricum 09:39Partial coverage+9 min+9 min
Mon 2 NovCastricum 09:39No data—
Fri 30 OctCastricum 09:380 min—
Thu 29 OctCastricum 09:39Partial coverage0 min—
Wed 28 OctCastricum 09:400 min—
Tue 27 OctCastricum 09:49Partial coverage0 min—
Mon 26 OctCastricum 09:390 min—
Sat 24 OctAmsterdam Sloterdijk 09:18+1 min+1 min
Fri 23 OctCastricum 09:400 min—
Thu 22 OctCastricum 09:390 min—
Wed 21 OctCastricum 09:390 min—
Tue 20 OctCastricum 09:390 min—
Mon 19 OctCastricum 09:42Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 09:140 min—
Thu 15 OctAmsterdam Sloterdijk 09:190 min—
Wed 14 OctAmsterdam Sloterdijk 09:190 min—
Tue 13 OctAmsterdam Sloterdijk 09:200 min—
Mon 12 OctAmsterdam Sloterdijk 09:200 min—
Fri 9 OctCastricum 09:53+12 min+12 min
Thu 8 OctCastricum 09:40Partial coverage+3 min+3 min
Wed 7 OctCastricum 09:400 min+1 min
Tue 6 OctCastricum 09:39Partial coverage+1 min—
Mon 5 OctCastricum 09:39No data—
Fri 2 OctCastricum 09:35No data—
Thu 1 OctCastricum 09:39No data—
Wed 30 SeptCastricum 09:47No data—
Tue 29 SeptCastricum 09:43No data—
Mon 28 SeptCastricum 09:39No data—