Train NS 2773 Alkmaar – Roermond

Alkmaar 19:01 → Roermond 21:31 Sun 2 h 30 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November +7 min

Next service: Sunday 19:01 from Alkmaar · Sun 22 Nov

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

Last 30 days

Arrival delay at Roermond, 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 15 Nov Max en route +7 min · last fix heading to Weert +7 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Sittard +6 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Amsterdam Amstel +3 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Ede-Wageningen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 43% · 3
  • 3–10 min 57% · 4
  • 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
  • 20% S n=5

Stops and timetable

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

Last 90 days, 7 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:09≈ on time ≈ on time
19:25≈ on time ≈ +1 min
19:31≈ on time ≈ +1 min
19:37 / 19:39≈ on time ≈ +1 min
19:47≈ on time ≈ +1 min
20:06 / 20:09≈ +1 min ≈ +2 min
20:36 / 20:38≈ +1 min ≈ +3 min
20:58 / 21:01≈ +1 min ≈ +3 min
21:18≈ +1 min ≈ +4 min
21:31+2 min +4 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
Sun 15 NovWeert 21:44Partial coverage+7 min+7 min
Sun 8 NovSittard 22:020 min—
Sat 7 NovSittard 21:590 min—
Sun 1 NovAmsterdam Amstel 20:13+3 min+3 min
Sun 25 OctSittard 22:02No data—
Sat 24 OctSittard 22:010 min—
Sun 18 OctSittard 22:09+6 min+7 min
Sat 17 OctAmsterdam Sloterdijk 19:46No data—
Sun 11 OctEde-Wageningen 20:53+3 min+3 min
Sun 4 OctSittard 22:02No data—
Sun 27 SeptSittard 22:17No data—
Sun 20 SeptUtrecht Centraal 20:25No data—
Sun 13 SeptSittard 22:01No data—
Sun 6 SeptWeert 21:32No data—
Sun 30 AugSittard 22:04No data—