Train NS 2720 Maastricht – Alkmaar

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

✓ Today’s run finished

Today, last fix heading to Castricum at 09:13 0 min

  1. Maastricht06:01
  2. Roermond06:31
  3. Eindhoven Centraal07:03
  4. Utrecht Centraal07:57
  5. Amsterdam Centraal08:26
  6. Castricum08:54
  7. Alkmaar09:03

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

Next departure 06:01 tomorrow · Maastricht
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 14 full · 8 partial · 0 no data
On-time · 90 days
97%
57/59 runs under 3 min
RT coverage: 50 full · 9 partial · 5 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: +3 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 +6 min · last fix heading to Castricum +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Castricum +3 min

Distribution · 90 days

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

  • Early 12% · 7
  • On time 85% · 50
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=13
  • 91% W n=11
  • 100% T n=12
  • 90% F n=10
  • 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, 59 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:01on time on time
06:16 / 06:17≈ on time ≈ on time
06:31 / 06:32≈ on time ≈ on time
06:46≈ on time ≈ on time
07:03 / 07:06≈ on time ≈ on time
07:26 / 07:30≈ on time ≈ on time
07:57 / 07:59≈ on time ≈ on time
08:17 / 08:18≈ on time ≈ +1 min
08:26 / 08:28≈ on time ≈ +1 min
08:33 / 08:35≈ on time ≈ +1 min
08:42≈ on time ≈ +1 min
08:54≈ on time ≈ +1 min
09:03on time on time

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 NovCastricum 09:13Partial coverage0 min—
Wed 4 NovCastricum 09:12Partial coverage+3 min+4 min
Tue 3 NovCastricum 09:14Partial coverage0 min—
Mon 2 NovCastricum 09:19Partial coverage0 min—
Fri 30 OctCastricum 09:19+2 min+3 min
Thu 29 OctCastricum 09:14Partial coverage0 min—
Wed 28 OctCastricum 09:390 min—
Tue 27 OctCastricum 09:090 min—
Mon 26 OctCastricum 09:110 min—
Fri 23 OctCastricum 09:130 min—
Thu 22 OctCastricum 09:090 min—
Wed 21 OctCastricum 09:090 min—
Tue 20 OctCastricum 09:090 min—
Mon 19 OctCastricum 09:09Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 08:430 min—
Thu 15 OctAmsterdam Sloterdijk 08:49+3 min+3 min
Wed 14 OctAmsterdam Sloterdijk 08:550 min—
Tue 13 OctAmsterdam Sloterdijk 08:490 min—
Mon 12 OctAmsterdam Sloterdijk 08:490 min—
Fri 9 OctCastricum 09:11+5 min+6 min
Thu 8 OctCastricum 09:09Partial coverage0 min—
Wed 7 OctCastricum 09:09Partial coverage+1 min—
Tue 6 OctCastricum 09:09Partial coverage+1 min—
Mon 5 OctAmsterdam Sloterdijk 12:160 min+2 min
Fri 2 OctAmsterdam Amstel 19:000 min+15 min
Thu 1 OctAmsterdam Amstel 18:570 min+4 min
Wed 30 SeptAmsterdam Amstel 19:180 min+7 min
Tue 29 SeptAmsterdam Amstel 00:420 min+15 min
Mon 28 SeptAmsterdam Amstel 00:370 min+8 min
Fri 25 SeptAmsterdam Amstel 10:510 min+32 min