Train NS 2779 Alkmaar – Roermond

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

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: Sunday 20:31 from Alkmaar · Sun 22 Nov

Next departure 20:31 Sunday · Alkmaar
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 1 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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 100% · 7
  • 3–10 min 0% · 0
  • 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
  • 100% 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
20:31on time on time
20:39≈ on time ≈ on time
20:55≈ on time ≈ on time
21:01≈ on time ≈ on time
21:07 / 21:09≈ on time ≈ on time
21:17≈ on time ≈ +1 min
21:36 / 21:39≈ on time ≈ +1 min
22:06 / 22:08≈ on time ≈ +1 min
22:28 / 22:31≈ on time ≈ +1 min
22:48≈ on time ≈ +2 min
23:01on time +2 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 23:03Partial coverage0 min+1 min
Sun 8 NovSittard 23:33+1 min+2 min
Sat 7 NovSittard 23:34+2 min+5 min
Sun 1 NovAmsterdam Amstel 21:320 min—
Sun 25 OctSittard 23:35No data—
Sat 24 OctEindhoven Centraal 23:310 min—
Sun 18 OctSittard 23:340 min—
Sun 11 OctEde-Wageningen 22:200 min—
Sun 4 OctSittard 23:34No data—
Sun 27 SeptSittard 23:36No data—
Sun 20 SeptUtrecht Centraal 21:53No data—
Sun 13 SeptSittard 23:44No data—
Sun 6 SeptWeert 23:01No data—
Sun 30 AugSittard 23:32No data—