Train NS 2763 Zaandam – Maastricht

Zaandam 16:49 → Maastricht 19:30 Daily 2 h 41 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:54

Heading to Maastricht 0 min

Estimated arrival at Maastricht 19:30 · 82 km/h

  1. Zaandam16:49
  2. Amsterdam Centraal17:02
  3. Amsterdam Amstel17:12
  4. 's-Hertogenbosch18:02
  5. Weert18:45
  6. Roermond18:58
  7. Maastricht19:30

Today it is running no worse than usual: typical arrival delay is +1 min; 67% of the last 9 runs arrived on time.

Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 8 full · 1 partial · 21 no data
On-time · 90 days
67%
6/9 runs under 3 min
RT coverage: 8 full · 1 partial · 77 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+20min
9 in 10 runs arrive with less than this
30 days: +20 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 7 Oct Max en route +43 min · last fix heading to 's-Hertogenbosch +43 min
  • Tue 6 Oct Max en route +15 min · last fix heading to 's-Hertogenbosch +14 min
  • Fri 9 Oct Max en route +8 min · last fix heading to Eindhoven Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 6
  • 3–10 min 11% · 1
  • 10–30 min 11% · 1
  • 30+ min 11% · 1

On-time by weekday

  • 100% M n=2
  • 0% T n=1
  • 50% W n=2
  • 100% T n=1
  • 0% F n=1
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

StopSched.Today
Zaandam
16:49
Amsterdam Sloterdijk
16:55 / 16:56
Amsterdam Centraal
17:02 / 17:04
Amsterdam Amstel
17:12
Utrecht Centraal
17:31 / 17:34
's-Hertogenbosch
18:02 / 18:04
Eindhoven Centraal
18:24 / 18:27
Weert
18:45
Roermond
18:58 / 19:00
Sittard
19:15 / 19:16
Maastricht
19:30

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.

Recent runs

DateLast stopFinalMax
Wed 14 OctWeert 18:49Partial coverage0 min—
Tue 13 OctEindhoven Centraal 18:41No data—
Mon 12 OctWeert 19:320 min—
Sun 11 OctEde-Wageningen 18:21+1 min—
Sat 10 OctSittard 19:37+2 min+4 min
Fri 9 OctEindhoven Centraal 19:47+7 min+8 min
Thu 8 OctUtrecht Centraal 19:310 min—
Wed 7 Oct's-Hertogenbosch 19:52+43 min+43 min
Tue 6 Oct's-Hertogenbosch 19:59+14 min+15 min
Mon 5 OctSchiedam Centrum 18:06+1 min—
Sun 4 OctSittard 19:33No data—
Sat 3 OctSittard 19:37No data—
Fri 2 OctWeert 19:01No data—
Thu 1 Oct's-Hertogenbosch 18:18No data—
Wed 30 Sept's-Hertogenbosch 18:18No data—
Tue 29 Sept's-Hertogenbosch 18:18No data—
Mon 28 Sept's-Hertogenbosch 18:18No data—
Sun 27 SeptSittard 19:34No data—
Sat 26 SeptAmsterdam Amstel 17:32No data—
Fri 25 SeptEindhoven Centraal 18:44No data—
Thu 24 SeptUtrecht Centraal 17:46No data—
Wed 23 Sept's-Hertogenbosch 18:18No data—
Tue 22 Sept's-Hertogenbosch 18:18No data—
Mon 21 Sept's-Hertogenbosch 18:18No data—
Sun 20 SeptUtrecht Centraal 17:53No data—
Sat 19 SeptUtrecht Centraal 17:53No data—
Fri 18 SeptWeert 19:01No data—
Thu 17 Sept's-Hertogenbosch 18:18No data—
Wed 16 Sept's-Hertogenbosch 18:18No data—
Tue 15 Sept's-Hertogenbosch 18:18No data—