Train NS 2733 Heerhugowaard – Maastricht

Heerhugowaard 08:46 → Maastricht 12:00 Mon, Tue, Wed, Thu, Fri, Sat 3 h 14 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 12:00 0 min

  1. Heerhugowaard08:46
  2. Alkmaar08:54
  3. Amsterdam Sloterdijk09:25
  4. Amsterdam Amstel09:42
  5. 's-Hertogenbosch10:32
  6. Sittard11:45
  7. Maastricht12:00

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

Next departure 08:46 tomorrow · Heerhugowaard
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 19 full · 1 partial · 6 no data
On-time · 90 days
78%
21/27 runs under 3 min
RT coverage: 26 full · 1 partial · 48 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: +4 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 9 Oct Max en route +13 min · last fix heading to Sittard +12 min
  • Sun 8 Nov Max en route +10 min · last fix heading to Sittard +9 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Weert +5 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Sittard +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 21
  • 3–10 min 19% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 75% W n=4
  • 100% T n=4
  • 50% F n=4
  • 83% S n=6
  • 0% S n=1

Stops and timetable

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

Last 90 days, 27 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:46on time on time
08:51≈ on time ≈ on time
08:54 / 08:57≈ on time ≈ on time
09:05≈ on time ≈ +1 min
09:19≈ on time ≈ +1 min
09:25 / 09:26≈ on time ≈ +1 min
09:32 / 09:34≈ on time ≈ +1 min
09:42≈ on time ≈ +2 min
10:01 / 10:04≈ on time ≈ +2 min
10:32 / 10:34≈ on time ≈ +3 min
10:54 / 10:57≈ on time ≈ +3 min
11:15≈ on time ≈ +4 min
11:28 / 11:30≈ on time ≈ +4 min
11:45 / 11:46≈ on time ≈ +5 min
12:00on 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
Mon 16 NovSittard 12:00Partial coverage0 min—
Sat 14 NovWeert 11:320 min+1 min
Fri 13 NovSittard 12:02+5 min+6 min
Thu 12 NovSittard 12:02+1 min+1 min
Wed 11 NovSittard 12:03+3 min+4 min
Tue 10 NovSittard 11:59+2 min+2 min
Mon 9 NovSittard 11:590 min—
Sun 8 NovSittard 12:19+9 min+10 min
Sat 7 NovSittard 11:590 min—
Fri 6 NovSittard 12:04No data—
Thu 5 NovSittard 12:02No data—
Wed 4 NovSittard 12:09+4 min+5 min
Tue 3 NovSittard 11:59No data—
Mon 2 NovSittard 12:090 min—
Sat 31 OctSittard 12:020 min—
Fri 30 OctSittard 12:02No data—
Thu 29 OctSittard 12:010 min—
Wed 28 OctSittard 12:00No data—
Tue 27 OctSittard 12:000 min—
Mon 26 OctSittard 12:00No data—
Sat 24 OctSittard 12:010 min—
Fri 23 OctSittard 12:010 min—
Thu 22 OctSittard 12:110 min—
Wed 21 OctSittard 12:000 min—
Tue 20 OctSittard 12:010 min—
Mon 19 OctSittard 12:010 min—
Sat 17 OctSittard 12:020 min—
Fri 16 OctSittard 12:070 min—
Thu 15 OctSittard 12:00No data—
Wed 14 OctSittard 12:01No data—