Train NS 2754 Nijmegen – Alkmaar

Nijmegen 15:28 → Alkmaar 17:29 Daily 2 h 01 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:28 from Nijmegen · Thu 5 Nov

Next departure 15:28 today · Nijmegen
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 22 full · 0 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

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

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

Worst days

  • Sat 24 Oct Max en route +10 min · last fix heading to Amsterdam Sloterdijk +10 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Castricum +10 min
  • Sun 18 Oct Max en route +11 min · last fix heading to Castricum +10 min
  • Sat 10 Oct Max en route +10 min · last fix heading to Castricum +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 67% T n=3
  • 100% F n=3
  • 50% S n=4
  • 50% S n=2

Stops and timetable

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

Last 90 days, 22 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
15:28on time on time
15:40 / 15:46≈ on time ≈ +1 min
15:56≈ on time ≈ +2 min
16:02≈ on time ≈ +3 min
16:21 / 16:24≈ on time ≈ +4 min
16:42≈ on time ≈ +6 min
16:50 / 16:53≈ on time ≈ +6 min
16:58≈ on time ≈ +7 min
17:06≈ on time ≈ +8 min
17:20≈ on time ≈ +9 min
17:29on time +9 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
Wed 4 NovCastricum 17:540 min—
Tue 3 NovCastricum 17:390 min—
Mon 2 NovCastricum 17:49No data—
Sun 1 NovCastricum 17:50Partial coverageNo data—
Sat 31 OctCastricum 17:35+1 min+1 min
Fri 30 OctMaastricht 17:560 min—
Thu 29 OctEindhoven Centraal 17:440 min—
Wed 28 OctCastricum 17:38No data—
Tue 27 OctCastricum 17:55No data—
Mon 26 OctCastricum 17:410 min—
Sun 25 OctCastricum 17:35No data—
Sat 24 OctAmsterdam Sloterdijk 17:28+10 min+10 min
Fri 23 OctCastricum 17:41No data—
Thu 22 OctCastricum 17:380 min—
Wed 21 OctCastricum 18:370 min—
Tue 20 OctCastricum 17:39No data—
Mon 19 OctCastricum 17:450 min—
Sun 18 OctCastricum 17:51+10 min+11 min
Sat 17 OctZaandam 17:240 min—
Fri 16 OctAmsterdam Sloterdijk 17:150 min—
Thu 15 OctAmsterdam Sloterdijk 17:17No data—
Wed 14 OctAmsterdam Sloterdijk 17:21No data—
Tue 13 OctAmsterdam Sloterdijk 17:350 min—
Mon 12 OctAmsterdam Sloterdijk 17:190 min—
Sun 11 OctCastricum 17:340 min—
Sat 10 OctCastricum 17:46+8 min+10 min
Fri 9 OctCastricum 17:38+2 min+4 min
Thu 8 OctCastricum 17:54+10 min+10 min
Wed 7 OctCastricum 17:38+1 min—
Tue 6 OctCastricum 17:450 min+6 min