Train NS 2752 Roermond – Alkmaar

Roermond 14:30 → Alkmaar 16:59 Daily 2 h 29 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +18 min

Next service: today 14:30 from Roermond · Mon 16 Nov

Next departure 14:30 today · Roermond
On-time · 30 days
70%
16/23 runs under 3 min
RT coverage: 22 full · 1 partial · 6 no data
On-time · 90 days
74%
25/34 runs under 3 min
RT coverage: 33 full · 1 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Mon 5 Oct Max en route +22 min · last fix heading to Castricum +22 min
  • Sun 15 Nov Max en route +18 min · last fix heading to Castricum +18 min
  • Sat 31 Oct Max en route +12 min · last fix heading to Castricum +12 min
  • Mon 9 Nov Max en route +8 min · last fix heading to Castricum +7 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Castricum +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 25
  • 3–10 min 18% · 6
  • 10–30 min 9% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 75% T n=4
  • 100% W n=5
  • 80% T n=5
  • 100% F n=6
  • 40% S n=5
  • 50% S n=4

Stops and timetable

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

Last 90 days, 34 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
14:30on time on time
14:44≈ on time ≈ +1 min
15:01 / 15:04≈ on time ≈ +1 min
15:23 / 15:24≈ on time ≈ +2 min
15:51 / 15:54≈ on time ≈ +3 min
16:12≈ on time ≈ +4 min
16:20 / 16:23≈ on time ≈ +4 min
16:28≈ on time ≈ +5 min
16:36≈ on time ≈ +5 min
16:50≈ on time ≈ +6 min
16:59on time +6 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 NovCastricum 17:29Partial coverage+18 min+18 min
Sat 14 NovCastricum 17:07+2 min+3 min
Fri 13 NovCastricum 17:08+2 min+2 min
Thu 12 NovCastricum 17:13+5 min+5 min
Wed 11 NovCastricum 17:09+3 min+3 min
Tue 10 NovCastricum 17:12+3 min+4 min
Mon 9 NovCastricum 17:19+7 min+8 min
Sun 8 NovCastricum 17:09+1 min—
Sat 7 NovCastricum 17:09+1 min+2 min
Fri 6 NovCastricum 17:04+1 min+1 min
Thu 5 NovCastricum 17:09No data—
Wed 4 NovCastricum 17:090 min—
Tue 3 NovCastricum 17:090 min—
Mon 2 NovCastricum 17:190 min—
Sun 1 NovCastricum 17:05No data—
Sat 31 OctCastricum 17:18+12 min+12 min
Fri 30 OctCastricum 17:050 min—
Thu 29 OctCastricum 17:080 min—
Wed 28 OctCastricum 17:230 min—
Tue 27 OctCastricum 17:10No data—
Mon 26 OctCastricum 17:08No data—
Sun 25 OctCastricum 17:04No data—
Sat 24 OctAmsterdam Sloterdijk 16:51+4 min+4 min
Fri 23 OctCastricum 17:110 min—
Thu 22 OctCastricum 17:120 min—
Wed 21 OctCastricum 17:120 min—
Tue 20 OctCastricum 17:19No data—
Mon 19 OctCastricum 17:150 min—
Sun 18 OctCastricum 17:14+6 min+7 min
Sat 17 OctZaandam 16:51No data—