Train NS 2747 Alkmaar – Maastricht

Alkmaar 12:27 → Maastricht 15: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 12:27 from Alkmaar · Sun 8 Nov

Next departure 12:27 today · Alkmaar
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 53 full · 1 partial · 31 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: 0 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

  • Fri 2 Oct Max en route +12 min · last fix heading to Sittard +11 min
  • Sat 15 Aug Max en route +4 min · last fix heading to Castricum +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Schiedam Centrum +3 min

Distribution · 90 days

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

  • Early 7% · 4
  • On time 87% · 47
  • 3–10 min 4% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=9
  • 100% W n=9
  • 100% T n=9
  • 88% F n=8
  • 88% S n=8
  • 100% S n=3

Stops and timetable

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

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