Train NS 2731 Heerhugowaard – Maastricht

Heerhugowaard 08:16 → Maastricht 11:30 Mon, Tue, Wed, Thu, Fri 3 h 14 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 11:29 +1 min

  1. Heerhugowaard08:16
  2. Alkmaar08:24
  3. Amsterdam Sloterdijk08:55
  4. Amsterdam Amstel09:12
  5. 's-Hertogenbosch10:02
  6. Sittard11:15
  7. Maastricht11:30

Next service: tomorrow 08:16 from Heerhugowaard · Wed 18 Nov

Next departure 08:16 tomorrow · Heerhugowaard
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 1 no data
On-time · 90 days
84%
27/32 runs under 3 min
RT coverage: 31 full · 1 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 4 Nov Max en route +10 min · last fix heading to Sittard +9 min
  • Wed 11 Nov Max en route +8 min · last fix heading to Sittard +7 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Sittard +6 min
  • Wed 7 Oct Max en route +26 min · last fix heading to Sittard +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 27
  • 3–10 min 16% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 50% W n=6
  • 100% T n=6
  • 60% F n=5
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

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