Train NS 2755 Alkmaar – Maastricht

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

Running now · updated 15:05

Heading to Maastricht 0 min

Estimated arrival at Maastricht 17:30 · 30 km/h

  1. Alkmaar14:27
  2. Zaandam14:49
  3. Amsterdam Centraal15:02
  4. Utrecht Centraal15:31
  5. Eindhoven Centraal16:24
  6. Roermond16:58
  7. Maastricht17:30

Today it is running no worse than usual: typical arrival delay is 0 min; 91% of the last 23 runs arrived on time.

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

  • Sat 10 Oct Max en route +20 min · last fix heading to Sittard +19 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Amsterdam Amstel +5 min

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 92% · 23
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 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, 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 10Today
14:27on time on time
14:35≈ on time ≈ on time
14:49≈ on time ≈ on time
14:55 / 14:56≈ on time ≈ on time
15:02 / 15:04≈ on time ≈ +1 min
15:12≈ on time ≈ +1 min
15:31 / 15:34≈ on time ≈ +1 min
16:02 / 16:04≈ on time ≈ +1 min
16:24 / 16:27≈ on time ≈ +2 min
16:45≈ on time ≈ +2 min
16:58 / 17:00≈ on time ≈ +2 min
17:15 / 17:16≈ on time ≈ +2 min
17:30on time +3 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
Thu 5 NovAmsterdam Centraal 15:04Partial coverage0 min—
Wed 4 NovSittard 17:34+2 min+3 min
Tue 3 NovSittard 17:29No data—
Mon 2 NovSittard 17:29No data—
Sun 1 NovAmsterdam Amstel 15:49+5 min+5 min
Sat 31 OctSittard 17:340 min—
Fri 30 OctSittard 17:570 min—
Thu 29 OctSittard 17:320 min—
Wed 28 OctSittard 17:310 min—
Tue 27 OctSittard 17:34No data—
Mon 26 OctSittard 17:31No data—
Sun 25 OctSittard 18:27No data—
Sat 24 OctSittard 17:310 min—
Fri 23 OctSittard 17:440 min—
Thu 22 OctSittard 17:32No data—
Wed 21 OctSittard 17:32No data—
Tue 20 OctAlkmaar 17:330 min—
Mon 19 OctSittard 17:590 min—
Sun 18 OctSittard 17:350 min—
Sat 17 OctSittard 17:320 min—
Fri 16 OctSittard 17:390 min—
Thu 15 OctSittard 17:300 min—
Wed 14 OctSittard 17:320 min—
Tue 13 OctSittard 17:310 min—
Mon 12 OctSittard 17:320 min—
Sun 11 OctEde-Wageningen 16:22+2 min+2 min
Sat 10 OctSittard 17:55+19 min+20 min
Fri 9 OctSittard 17:39+3 min+6 min
Thu 8 OctSittard 17:310 min—
Wed 7 OctSittard 17:320 min—