Train NS 2935 Enkhuizen – Roermond

Enkhuizen 09:09 → Roermond 12:00 Fri, Sat, Sun 2 h 51 min · 14 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November +1 min

Next service: Friday 09:09 from Enkhuizen · Fri 20 Nov

Next departure 09:09 Friday · Enkhuizen
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 2 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 12 full · 1 partial · 22 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: +1 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

  • Fri 9 Oct Max en route +6 min · last fix heading to Amsterdam Sloterdijk +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 75% F n=4
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 13 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
09:09on time on time
09:13≈ on time ≈ on time
09:16 / 09:17≈ on time ≈ on time
09:21 / 09:22≈ on time ≈ on time
09:29≈ on time ≈ on time
09:33 / 09:34≈ on time ≈ on time
09:59 / 10:01≈ on time ≈ +1 min
10:07 / 10:09≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:36 / 10:39≈ on time ≈ +1 min
11:06 / 11:08≈ on time ≈ +2 min
11:28 / 11:30≈ on time ≈ +2 min
11:47≈ on time ≈ +2 min
12:00on 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 12:04Partial coverage+1 min+2 min
Sat 14 NovAmsterdam Sloterdijk 10:190 min—
Fri 13 NovAmsterdam Sloterdijk 10:180 min—
Fri 6 NovAmsterdam Sloterdijk 10:18No data—
Sun 1 NovArnhem Centraal 11:350 min—
Sat 31 OctAmsterdam Sloterdijk 10:200 min—
Fri 30 OctAmsterdam Sloterdijk 10:180 min—
Sun 25 OctSittard 12:39No data—
Sun 18 OctSittard 12:39+2 min+4 min
Sat 17 OctAmsterdam Sloterdijk 10:200 min—
Fri 16 OctAmsterdam Sloterdijk 10:190 min—
Sun 11 OctEde-Wageningen 11:22+2 min+2 min
Sat 10 OctAmsterdam Sloterdijk 10:19+2 min+2 min
Fri 9 OctAmsterdam Sloterdijk 10:19+6 min+6 min
Mon 5 OctSittard 12:340 min—
Sun 4 OctSittard 12:33No data—
Fri 2 OctAmsterdam Sloterdijk 10:19No data—
Sun 27 SeptSittard 12:34No data—
Sat 26 SeptAmsterdam Sloterdijk 10:21No data—
Fri 25 SeptAmsterdam Sloterdijk 10:19No data—
Sun 20 SeptUtrecht Centraal 10:53No data—
Sat 19 SeptAmsterdam Sloterdijk 10:20No data—
Fri 18 SeptAmsterdam Sloterdijk 10:18No data—
Sun 13 SeptSittard 12:39No data—
Sat 12 SeptAmsterdam Sloterdijk 10:21No data—
Fri 11 SeptAmsterdam Sloterdijk 10:20No data—
Sun 6 SeptWeert 12:02No data—
Sat 5 SeptAmsterdam Sloterdijk 10:20No data—
Fri 4 SeptAmsterdam Sloterdijk 10:19No data—
Sun 30 AugSittard 12:31No data—