Train NS 2751 Alkmaar – Maastricht

Alkmaar 13:27 → Maastricht 16:30 Daily 3 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 13:27 from Alkmaar · Sun 8 Nov

Next departure 13:27 today · Alkmaar
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 50 full · 1 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Maastricht, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +4 min · last fix heading to Utrecht Centraal +4 min

Distribution · 90 days

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

  • Early 12% · 6
  • On time 86% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=8
  • 100% F n=7
  • 100% S n=8
  • 83% S n=6

Stops and timetable

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

Last 90 days, 51 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
13:27on time on time
13:35≈ on time ≈ on time
13:49≈ on time ≈ on time
13:55 / 13:56≈ on time ≈ on time
14:02 / 14:04≈ on time ≈ on time
14:12≈ on time ≈ on time
14:31 / 14:34≈ on time ≈ on time
15:02 / 15:04≈ on time ≈ on time
15:24 / 15:27≈ on time ≈ on time
15:45≈ on time ≈ on time
15:58 / 16:00≈ on time ≈ +1 min
16:15 / 16:16≈ on time ≈ on time
16:30on 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
Sat 7 NovSittard 16:29Partial coverage0 min—
Fri 6 NovSittard 16:29No data—
Thu 5 NovSittard 16:300 min—
Wed 4 NovSittard 16:340 min—
Tue 3 NovSittard 16:29No data—
Mon 2 NovSittard 16:340 min—
Sun 1 NovUtrecht Centraal 14:55+4 min+4 min
Sat 31 OctSittard 16:310 min—
Fri 30 OctSittard 16:46No data—
Thu 29 OctSittard 16:320 min—
Wed 28 OctSittard 16:31No data—
Tue 27 OctSittard 16:340 min—
Mon 26 OctSittard 16:34No data—
Sun 25 OctSittard 16:33No data—
Sat 24 OctSittard 16:310 min—
Fri 23 OctSittard 16:310 min—
Thu 22 OctSittard 16:310 min—
Wed 21 OctSittard 16:310 min—
Tue 20 OctSittard 16:310 min—
Mon 19 OctSittard 16:360 min—
Sun 18 OctSittard 16:33+1 min+2 min
Sat 17 OctSittard 16:310 min—
Fri 16 OctSittard 16:370 min—
Thu 15 OctSittard 16:31No data—
Wed 14 OctSittard 16:340 min—
Tue 13 OctSittard 16:31No data—
Mon 12 OctSittard 16:320 min—
Sun 11 OctEde-Wageningen 15:21+1 min—
Sat 10 OctSittard 16:350 min—
Fri 9 OctSittard 16:350 min—