Train NS 2779 Alkmaar – Nijmegen

Alkmaar 20:31 → Nijmegen 22:33 Sat, Sun 2 h 02 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 20:31 from Alkmaar · Sat 7 Nov

Next departure 20:31 today · Alkmaar
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 1 no data
On-time · 90 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 8 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)

Last 30 days

Arrival delay at Nijmegen, 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

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

  • Early 0% · 0
  • On time 100% · 4
  • 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=1
  • 100% S n=3

Stops and timetable

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

Not enough runs yet to work out the usual delay by stop.

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
Sun 1 NovAmsterdam Amstel 21:32Partial coverage0 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—
Sun 16 AugAmsterdam Amstel 21:32No data—