Train NS 2757 Alkmaar – Maastricht

Alkmaar 14:57 → Maastricht 18:00 Daily 3 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 18:04 0 min

  1. Alkmaar14:57
  2. Zaandam15:19
  3. Amsterdam Centraal15:32
  4. Utrecht Centraal16:01
  5. Eindhoven Centraal16:54
  6. Sittard17:45
  7. Maastricht18:00

Next service: tomorrow 14:57 from Alkmaar · Fri 6 Nov

Next departure 14:57 tomorrow · Alkmaar
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 22 full · 4 partial · 4 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 24 full · 4 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Mon 5 Oct Max en route +9 min · last fix heading to Schiedam Centrum +9 min
  • Sat 24 Oct Max en route +8 min · last fix heading to Sittard +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
14:57on time on time
15:05≈ on time ≈ on time
15:19≈ on time ≈ on time
15:25 / 15:26≈ on time ≈ on time
15:32 / 15:34≈ on time ≈ on time
15:42≈ on time ≈ +1 min
16:01 / 16:04≈ on time ≈ +1 min
16:32 / 16:34≈ on time ≈ +1 min
16:54 / 16:57≈ on time ≈ +2 min
17:15≈ on time ≈ +2 min
17:28 / 17:30≈ on time ≈ +2 min
17:45 / 17:46≈ on time ≈ +2 min
18:00on 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 NovSittard 18:04Partial coverage0 min—
Wed 4 NovSittard 18:040 min—
Tue 3 NovSittard 17:590 min—
Mon 2 NovSittard 18:04No data—
Sun 1 NovAmsterdam Amstel 16:11+1 min+1 min
Sat 31 OctSittard 18:020 min+4 min
Fri 30 OctSittard 18:070 min—
Thu 29 OctSittard 18:02Partial coverage0 min—
Wed 28 OctSittard 18:010 min—
Tue 27 OctSittard 18:020 min—
Mon 26 OctSittard 18:28+2 min+2 min
Sun 25 OctSittard 18:05No data—
Sat 24 OctSittard 18:13+6 min+8 min
Fri 23 OctSittard 18:010 min—
Thu 22 OctSittard 18:02Partial coverage0 min—
Wed 21 OctSittard 18:02No data—
Tue 20 OctSittard 18:020 min—
Mon 19 OctSittard 18:080 min—
Sun 18 OctEindhoven Centraal 17:140 min+9 min
Sat 17 OctSittard 18:120 min—
Fri 16 OctSittard 18:260 min—
Thu 15 OctSittard 18:030 min—
Wed 14 OctSittard 18:02No data—
Tue 13 OctSittard 18:020 min—
Mon 12 OctSittard 18:020 min—
Sun 11 OctEde-Wageningen 16:50+1 min—
Sat 10 OctSittard 18:030 min—
Fri 9 OctSittard 18:15+3 min+5 min
Thu 8 OctRoermond 18:02Partial coverage0 min—
Wed 7 OctSittard 18:010 min—