Train NS 2739 Alkmaar – Maastricht

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

Running now · updated 11:16

Heading to Maastricht No data

Estimated arrival at Maastricht 13:30 · 160 km/h

  1. Alkmaar10:27
  2. Zaandam10:49
  3. Amsterdam Centraal11:02
  4. Utrecht Centraal11:31
  5. Eindhoven Centraal12:24
  6. Roermond12:58
  7. Maastricht13:30
On-time · 30 days
84%
21/25 runs under 3 min
RT coverage: 21 full · 4 partial · 5 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 21 full · 5 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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 +8 min · last fix heading to Arnhem Centraal +8 min
  • Fri 9 Oct Max en route +9 min · last fix heading to Sittard +7 min
  • Wed 7 Oct Max en route +9 min · last fix heading to Sittard +7 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Sittard +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 22
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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