Train NS 2772 Maastricht – Zaandam

Maastricht 19:01 → Zaandam 21:41 Sat, Sun 2 h 40 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +2 min

Next service: today 19:01 from Maastricht · Sun 8 Nov

Next departure 19:01 today · Maastricht
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 4 full · 1 partial · 1 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 4 full · 1 partial · 8 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zaandam, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +6 min · last fix heading to Castricum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 20% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 5 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
19:01on time on time
19:16 / 19:17— —
19:31 / 19:32— —
19:46— —
20:03 / 20:06— —
20:26 / 20:30— —
20:57 / 20:59— —
21:17— —
21:25 / 21:28— —
21:33 / 21:35— —
21:41— —

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 NovAmsterdam Sloterdijk 21:49Partial coverage+2 min+2 min
Sun 1 NovCastricum 22:04+1 min—
Sun 25 OctCastricum 22:24No data—
Sat 24 OctAmsterdam Centraal 22:010 min—
Sun 18 OctCastricum 22:08+3 min+6 min
Sun 11 OctCastricum 22:040 min—
Sun 4 OctBovenkarspel Flora 22:34No data—
Sun 27 SeptCastricum 22:05No data—
Sun 20 SeptCastricum 22:04No data—
Sun 13 SeptCastricum 22:13No data—
Sun 6 SeptCastricum 22:05No data—
Sun 30 AugCastricum 22:04No data—
Sun 16 AugCastricum 22:05No data—