Train NS 2729 Heerhugowaard – Maastricht

Heerhugowaard 07:46 → Maastricht 11:00 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:04 +1 min

  1. Heerhugowaard07:46
  2. Alkmaar07:54
  3. Amsterdam Sloterdijk08:25
  4. Amsterdam Amstel08:42
  5. 's-Hertogenbosch09:32
  6. Sittard10:45
  7. Maastricht11:00

Next service: tomorrow 07:46 from Heerhugowaard · Tue 17 Nov

Next departure 07:46 tomorrow · Heerhugowaard
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 1 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 29 full · 1 partial · 35 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: +3 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 13 Nov Max en route +16 min · last fix heading to Sittard +16 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Sittard +4 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 27
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=6
  • 100% W n=5
  • 100% T n=6
  • 80% F n=5
  • 50% 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, 30 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
07:46on time on time
07:51≈ on time ≈ on time
07:54 / 07:57≈ on time ≈ on time
08:05≈ on time ≈ on time
08:19≈ on time ≈ on time
08:25 / 08:26≈ on time ≈ on time
08:32 / 08:34≈ on time ≈ on time
08:42≈ on time ≈ +1 min
09:01 / 09:04≈ on time ≈ +1 min
09:32 / 09:34≈ on time ≈ +1 min
09:54 / 09:57≈ on time ≈ +1 min
10:15≈ on time ≈ +1 min
10:28 / 10:30≈ on time ≈ +2 min
10:45 / 10:46≈ on time ≈ +2 min
11:00on time +2 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
Mon 16 NovSittard 11:04Partial coverage+1 min+1 min
Fri 13 NovSittard 11:02+16 min+16 min
Thu 12 NovSittard 11:000 min+3 min
Wed 11 NovSittard 10:590 min—
Tue 10 NovSittard 10:590 min—
Mon 9 NovSittard 11:09+4 min+4 min
Sun 8 NovSittard 10:590 min—
Sat 7 NovSittard 10:59+1 min+1 min
Fri 6 NovSittard 11:02No data—
Thu 5 NovSittard 11:290 min—
Wed 4 NovSittard 11:09+1 min+1 min
Tue 3 NovSittard 11:090 min—
Mon 2 NovSittard 11:090 min—
Fri 30 OctSittard 11:020 min—
Thu 29 OctSittard 11:010 min—
Wed 28 OctSittard 11:020 min—
Tue 27 OctSittard 11:000 min—
Mon 26 OctSittard 11:010 min—
Sat 24 OctSittard 11:08+4 min+4 min
Fri 23 OctSittard 11:130 min—
Thu 22 OctSittard 11:240 min—
Wed 21 OctSittard 11:010 min—
Tue 20 OctSittard 11:000 min—
Mon 19 OctEindhoven Centraal 11:230 min—
Fri 16 OctSittard 11:050 min—
Thu 15 OctSittard 11:010 min—
Wed 14 OctSittard 11:01No data—
Tue 13 OctSittard 11:010 min—
Mon 12 OctSittard 11:20No data—
Fri 9 OctSittard 11:030 min+2 min