Train NS 2728 Maastricht – Alkmaar

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

✓ Today’s run finished

Today, last fix heading to Castricum at 11:09 No data

  1. Maastricht08:01
  2. Roermond08:31
  3. Eindhoven Centraal09:03
  4. Utrecht Centraal09:57
  5. Amsterdam Centraal10:25
  6. Castricum10:54
  7. Alkmaar11:03

Next service: tomorrow 08:01 from Maastricht · Sat 7 Nov

Next departure 08:01 tomorrow · Maastricht
On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 22 full · 3 partial · 1 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 23 full · 4 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Thu 8 Oct Max en route +10 min · last fix heading to Castricum +10 min
  • Fri 9 Oct Max en route +8 min · last fix heading to Castricum +7 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Castricum +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Castricum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 11% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
08:01on time on time
08:16 / 08:17≈ on time ≈ on time
08:31 / 08:32≈ on time ≈ on time
08:46≈ on time ≈ on time
09:03 / 09:06≈ on time ≈ on time
09:26 / 09:30≈ on time ≈ on time
09:57 / 09:59≈ on time ≈ on time
10:17≈ on time ≈ on time
10:25 / 10:28≈ on time ≈ +1 min
10:33 / 10:35≈ on time ≈ +1 min
10:42≈ on time ≈ +1 min
10:54≈ on time ≈ +1 min
11: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
Fri 6 NovCastricum 11:09No data—
Thu 5 NovCastricum 11:09Partial coverage0 min—
Wed 4 NovCastricum 11:12Partial coverage+4 min+4 min
Tue 3 NovCastricum 11:130 min—
Mon 2 NovCastricum 11:090 min—
Sat 31 OctCastricum 11:040 min—
Fri 30 OctCastricum 11:040 min—
Thu 29 OctCastricum 11:090 min—
Wed 28 OctCastricum 11:090 min—
Tue 27 OctCastricum 11:090 min—
Mon 26 OctCastricum 11:090 min—
Sat 24 OctAmsterdam Sloterdijk 10:480 min—
Fri 23 OctCastricum 11:470 min—
Thu 22 OctCastricum 11:110 min—
Wed 21 OctCastricum 11:090 min—
Tue 20 OctCastricum 11:090 min—
Mon 19 OctCastricum 11:090 min—
Sat 17 OctZaandam 10:510 min—
Fri 16 OctAmsterdam Sloterdijk 10:430 min—
Thu 15 Oct's-Hertogenbosch 10:580 min—
Wed 14 OctAmsterdam Sloterdijk 10:510 min—
Tue 13 OctAmsterdam Sloterdijk 10:510 min—
Mon 12 OctAmsterdam Sloterdijk 10:490 min—
Sat 10 OctCastricum 11:05+1 min—
Fri 9 OctCastricum 11:15+7 min+8 min
Thu 8 OctCastricum 11:10Partial coverage+10 min+10 min
Wed 7 OctCastricum 12:02Partial coverage0 min—
Tue 6 OctCastricum 11:13+4 min+5 min
Mon 5 OctCastricum 11:33No data—
Sat 3 OctDuivendrecht 10:25No data—