Train NS 2724 Maastricht – Alkmaar

Maastricht 07:01 → Alkmaar 10:03 Daily 3 h 02 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Castricum at 10:09 +2 min

  1. Maastricht07:01
  2. Roermond07:31
  3. Eindhoven Centraal08:03
  4. Utrecht Centraal08:57
  5. Amsterdam Centraal09:25
  6. Castricum09:54
  7. Alkmaar10:03

Next service: tomorrow 07:01 from Maastricht · Sun 8 Nov

Next departure 07:01 tomorrow · Maastricht
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 1 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 24 full · 1 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
07:01on time on time
07:16 / 07:17≈ on time ≈ on time
07:31 / 07:32≈ on time ≈ on time
07:46≈ on time ≈ on time
08:03 / 08:06≈ on time ≈ on time
08:26 / 08:30≈ on time ≈ +1 min
08:57 / 08:59≈ on time ≈ +1 min
09:17≈ on time ≈ +1 min
09:25 / 09:28≈ on time ≈ +1 min
09:33 / 09:35≈ on time ≈ +1 min
09:42≈ on time ≈ +1 min
09:54≈ on time ≈ +1 min
10:03on time +1 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
Sat 7 NovCastricum 10:09Partial coverage+2 min+3 min
Fri 6 NovZaandam 09:49No data—
Thu 5 NovCastricum 10:140 min—
Wed 4 NovCastricum 10:140 min—
Tue 3 NovCastricum 10:140 min—
Mon 2 NovCastricum 10:090 min—
Fri 30 OctCastricum 10:050 min—
Thu 29 OctCastricum 10:110 min—
Wed 28 OctCastricum 10:100 min—
Tue 27 OctCastricum 10:100 min—
Mon 26 OctCastricum 10:090 min—
Sat 24 OctAmsterdam Sloterdijk 09:49+1 min+2 min
Fri 23 OctCastricum 10:110 min—
Thu 22 OctCastricum 10:120 min—
Wed 21 OctCastricum 10:100 min—
Tue 20 OctCastricum 10:090 min—
Mon 19 OctCastricum 10:100 min—
Fri 16 OctAmsterdam Sloterdijk 09:450 min—
Thu 15 OctAmsterdam Amstel 10:580 min—
Wed 14 OctAmsterdam Sloterdijk 09:520 min—
Tue 13 OctAmsterdam Sloterdijk 09:490 min—
Mon 12 OctAmsterdam Sloterdijk 09:490 min—
Fri 9 OctCastricum 10:06+1 min+1 min
Thu 8 OctCastricum 10:10+1 min+2 min
Wed 7 OctCastricum 10:11+2 min+2 min
Tue 6 OctCastricum 10:220 min+13 min
Mon 5 OctCastricum 10:11No data—
Fri 2 OctCastricum 10:05No data—
Thu 1 OctCastricum 10:10No data—
Wed 30 SeptCastricum 10:09No data—