Train NS 2781 Zaandam – Maastricht

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 21:19 from Zaandam · Sun 8 Nov

Next departure 21:19 today · Zaandam
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
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Sun 1 Nov Max en route +7 min · last fix heading to Castricum +7 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
21:19on time on time
21:25 / 21:26— —
21:32 / 21:35— —
21:43— —
22:01 / 22:04— —
22:32 / 22:34— —
22:54 / 22:57— —
23:15— —
23:28 / 23:30— —
23:45 / 23:46— —
00:00— —

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 NovWeert 23:59Partial coverage0 min—
Sun 1 NovCastricum 23:04+7 min+7 min
Sun 25 OctSittard 00:05No data—
Sat 24 OctAmsterdam Centraal 00:020 min—
Sun 18 OctSittard 00:06+1 min+1 min
Sun 11 OctEde-Wageningen 22:500 min—
Sun 4 OctSittard 00:02No data—
Sun 27 SeptSittard 00:03No data—
Sun 20 SeptUtrecht Centraal 22:23No data—
Sun 13 SeptSittard 00:04No data—
Sun 6 SeptWeert 23:42No data—
Sun 30 AugSittard 00:02No data—
Sun 16 AugAmsterdam Amstel 22:02No data—