Train NS 2736 Maastricht – Alkmaar

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

Running now · updated 10:43

Heading to Alkmaar No data

Estimated arrival at Alkmaar 13:03 · 88 km/h

  1. Maastricht10:01
  2. Roermond10:31
  3. Eindhoven Centraal11:03
  4. Utrecht Centraal11:57
  5. Amsterdam Centraal12:25
  6. Zaandam12:42
  7. Alkmaar13:03
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 20 full · 4 partial · 6 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 22 full · 5 partial · 59 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: +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

  • Wed 4 Nov Max en route +25 min · last fix heading to Castricum +25 min
  • Sat 10 Oct Max en route +10 min · last fix heading to Castricum +10 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Castricum +6 min
  • Wed 7 Oct 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 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 60% W n=5
  • 100% T n=5
  • 100% F n=3
  • 75% S n=4
  • 67% S n=3

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 10Today
10:01on time on time
10:16 / 10:17≈ on time ≈ on time
10:31 / 10:32≈ on time ≈ on time
10:46≈ on time ≈ +1 min
11:03 / 11:06≈ on time ≈ +1 min
11:26 / 11:30≈ on time ≈ +1 min
11:57 / 11:59≈ on time ≈ +1 min
12:17≈ on time ≈ +2 min
12:25 / 12:28≈ on time ≈ +2 min
12:33 / 12:35≈ on time ≈ +2 min
12:42≈ on time ≈ +2 min
12:54≈ on time ≈ +2 min
13:03on time +2 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 NovWeert 10:39No data—
Thu 5 NovCastricum 13:08Partial coverage0 min—
Wed 4 NovCastricum 13:13Partial coverage+25 min+25 min
Tue 3 NovCastricum 13:120 min—
Mon 2 NovCastricum 13:120 min—
Sun 1 NovDen Helder Zuid 14:07+2 min+2 min
Sat 31 OctCastricum 13:050 min—
Fri 30 OctCastricum 13:04No data—
Thu 29 OctCastricum 13:09Partial coverage0 min—
Wed 28 OctCastricum 13:090 min—
Tue 27 OctCastricum 13:10No data—
Mon 26 OctCastricum 13:12No data—
Sun 25 OctCastricum 13:25No data—
Sat 24 OctAmsterdam Sloterdijk 12:49+1 min+1 min
Fri 23 OctCastricum 13:090 min—
Thu 22 OctCastricum 13:100 min—
Wed 21 OctCastricum 13:090 min—
Tue 20 OctCastricum 13:090 min—
Mon 19 OctCastricum 13:090 min—
Sun 18 OctCastricum 13:05+6 min+6 min
Sat 17 OctZaandam 12:570 min—
Fri 16 OctAmsterdam Sloterdijk 12:440 min—
Thu 15 OctAmsterdam Sloterdijk 12:490 min—
Wed 14 OctAmsterdam Sloterdijk 12:510 min—
Tue 13 OctAmsterdam Sloterdijk 12:49No data—
Mon 12 OctAmsterdam Sloterdijk 12:490 min—
Sun 11 OctCastricum 13:050 min—
Sat 10 OctCastricum 13:20+10 min+10 min
Fri 9 OctCastricum 13:040 min—
Thu 8 OctCastricum 13:12Partial coverage+3 min+3 min