Train NS 2765 Alkmaar – Roermond

Alkmaar 17:01 → Roermond 19:30 Daily 2 h 29 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +14 min

Next service: today 17:01 from Alkmaar · Mon 16 Nov

Next departure 17:01 today · Alkmaar
On-time · 30 days
78%
21/27 runs under 3 min
RT coverage: 26 full · 1 partial · 2 no data
On-time · 90 days
79%
31/39 runs under 3 min
RT coverage: 38 full · 1 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +8 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 +14 min · last fix heading to Weert +14 min
  • Tue 6 Oct Max en route +12 min · last fix heading to Utrecht Centraal +12 min
  • Wed 4 Nov Max en route +11 min · last fix heading to Utrecht Centraal +11 min
  • Thu 12 Nov Max en route +11 min · last fix heading to Utrecht Centraal +10 min
  • Fri 23 Oct Max en route +6 min · last fix heading to Weert +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 31
  • 3–10 min 13% · 5
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 60% T n=5
  • 83% W n=6
  • 80% T n=5
  • 67% F n=6
  • 100% S n=6
  • 60% S n=5

Stops and timetable

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

Last 90 days, 39 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
17:01on time on time
17:09≈ on time ≈ on time
17:25≈ on time ≈ +1 min
17:31≈ on time ≈ +1 min
17:37 / 17:39≈ on time ≈ +1 min
17:50≈ on time ≈ +2 min
18:06 / 18:09≈ on time ≈ +2 min
18:36 / 18:38≈ on time ≈ +4 min
18:58 / 19:00≈ on time ≈ +4 min
19:17≈ on time ≈ +5 min
19:30on 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 NovWeert 19:47Partial coverage+14 min+14 min
Sat 14 NovWeert 19:33+1 min+1 min
Fri 13 Nov's-Hertogenbosch 18:52+5 min+6 min
Thu 12 NovUtrecht Centraal 20:23+10 min+11 min
Wed 11 NovUtrecht Centraal 20:04+1 min+1 min
Tue 10 NovUtrecht Centraal 20:08+4 min+4 min
Mon 9 NovAlkmaar 20:020 min+1 min
Sun 8 NovSittard 20:04+1 min+1 min
Sat 7 NovSittard 19:590 min+2 min
Fri 6 Nov's-Hertogenbosch 18:59+1 min—
Thu 5 NovUtrecht Centraal 20:280 min—
Wed 4 NovUtrecht Centraal 20:22+11 min+11 min
Tue 3 NovUtrecht Centraal 18:590 min—
Mon 2 NovUtrecht Centraal 19:590 min—
Sun 1 NovAmsterdam Amstel 18:11+1 min+1 min
Sat 31 OctSittard 20:16+1 min+4 min
Fri 30 Oct's-Hertogenbosch 18:520 min—
Thu 29 OctAmsterdam Amstel 20:010 min—
Wed 28 OctUtrecht Centraal 18:56+1 min+1 min
Tue 27 OctUtrecht Centraal 20:23No data—
Mon 26 OctUtrecht Centraal 18:550 min—
Sun 25 OctSittard 20:32No data—
Sat 24 OctSittard 20:040 min—
Fri 23 OctWeert 20:14+6 min+6 min
Thu 22 Oct's-Hertogenbosch 18:560 min—
Wed 21 Oct's-Hertogenbosch 20:020 min—
Tue 20 OctZaandam 19:000 min—
Mon 19 Oct's-Hertogenbosch 20:040 min—
Sun 18 OctSittard 20:020 min+2 min
Sat 17 OctSittard 20:020 min—