Train NS 2735 Alkmaar – Maastricht

Alkmaar 09:27 → Maastricht 12:30 Mon, Tue, Wed, Thu, Fri, Sat 3 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 09:27 from Alkmaar · Wed 18 Nov

Next departure 09:27 today · Alkmaar
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 34 full · 1 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 11 Nov Max en route +11 min · last fix heading to Sittard +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 80% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 100% S n=1

Stops and timetable

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

Last 90 days, 35 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
09:27on time on time
09:35≈ on time ≈ on time
09:49≈ on time ≈ on time
09:55 / 09:56≈ on time ≈ on time
10:02 / 10:04≈ on time ≈ on time
10:12≈ on time ≈ on time
10:31 / 10:34≈ on time ≈ on time
11:02 / 11:04≈ on time ≈ +1 min
11:24 / 11:27≈ on time ≈ +1 min
11:45≈ on time ≈ +1 min
11:58 / 12:00≈ on time ≈ +1 min
12:15 / 12:16≈ on time ≈ +1 min
12:30on time +1 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
Tue 17 NovSittard 12:34Partial coverage+2 min+4 min
Mon 16 NovSittard 12:34+1 min+1 min
Sat 14 NovWeert 11:59+1 min+1 min
Fri 13 NovSittard 12:33+2 min+2 min
Thu 12 NovSittard 12:290 min—
Wed 11 NovSittard 12:53+11 min+11 min
Tue 10 NovSittard 12:290 min+2 min
Mon 9 NovSittard 12:290 min—
Sun 8 NovSittard 12:34+2 min+2 min
Sat 7 NovSittard 12:32+1 min+1 min
Fri 6 NovSittard 12:34No data—
Thu 5 NovSittard 12:320 min—
Wed 4 NovSittard 12:290 min—
Tue 3 Nov's-Hertogenbosch 12:290 min—
Mon 2 NovSittard 12:290 min—
Sat 31 OctSittard 12:370 min+3 min
Fri 30 OctSittard 12:340 min—
Thu 29 OctSittard 12:300 min—
Wed 28 OctSittard 12:320 min—
Tue 27 OctSittard 12:310 min—
Mon 26 OctSittard 12:300 min—
Sat 24 OctSittard 12:31+1 min+1 min
Fri 23 OctSittard 12:540 min—
Thu 22 OctSittard 12:550 min—
Wed 21 OctSittard 12:310 min—
Tue 20 OctSittard 12:310 min—
Mon 19 OctSittard 12:360 min—
Sat 17 OctSittard 12:340 min—
Fri 16 OctSittard 12:340 min—
Thu 15 OctSittard 12:59No data—