Train NS 2933 Enkhuizen – Roermond

Enkhuizen 08:39 → Roermond 11:30 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: tomorrow 08:39 from Enkhuizen · Fri 20 Nov

Next departure 08:39 tomorrow · Enkhuizen
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 4 full · 1 partial · 3 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Sat 10 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 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
  • 100% F n=3
  • 75% 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, 11 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
08:39on time on time
08:43≈ on time ≈ on time
08:46 / 08:47≈ on time ≈ on time
08:51 / 08:52≈ on time ≈ on time
08:59≈ on time ≈ on time
09:03 / 09:04≈ on time ≈ on time
09:29 / 09:31≈ on time ≈ on time
09:37 / 09:39≈ on time ≈ +1 min
09:47≈ on time ≈ +1 min
10:06 / 10:09≈ on time ≈ +1 min
10:36 / 10:38≈ on time ≈ +1 min
10:58 / 11:00≈ on time ≈ +1 min
11:17≈ on time ≈ +1 min
11:30on 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 11:33Partial coverage+1 min+1 min
Sat 14 NovAmsterdam Sloterdijk 09:480 min—
Fri 13 NovAmsterdam Sloterdijk 09:49+1 min—
Fri 6 NovAmsterdam Sloterdijk 09:48No data—
Sun 1 NovArnhem Centraal 11:040 min—
Sat 31 OctAmsterdam Sloterdijk 09:480 min—
Fri 30 OctAmsterdam Sloterdijk 09:48No data—
Sun 25 OctSittard 12:04No data—
Sun 18 OctSittard 12:050 min—
Sat 17 OctAmsterdam Sloterdijk 09:480 min—
Fri 16 OctAmsterdam Sloterdijk 09:490 min—
Sun 11 OctEde-Wageningen 10:50+1 min+1 min
Sat 10 OctAmsterdam Sloterdijk 09:50+4 min+4 min
Fri 9 OctAmsterdam Sloterdijk 09:500 min+2 min
Mon 5 OctSittard 12:07No data—
Sun 4 OctSittard 12:02No data—
Fri 2 OctAmsterdam Sloterdijk 09:49No data—
Sun 27 SeptSittard 12:01No data—
Sat 26 SeptAmsterdam Sloterdijk 09:48No data—
Fri 25 SeptAmsterdam Sloterdijk 09:48No data—
Sun 20 SeptUtrecht Centraal 10:23No data—
Sat 19 SeptAmsterdam Sloterdijk 09:48No data—
Fri 18 SeptAmsterdam Sloterdijk 09:49No data—
Sun 13 SeptSittard 12:02No data—
Sat 12 SeptAmsterdam Sloterdijk 09:49No data—
Fri 11 SeptAmsterdam Sloterdijk 09:49No data—
Sun 6 SeptWeert 11:31No data—
Sat 5 SeptAmsterdam Sloterdijk 09:48No data—
Fri 4 SeptAmsterdam Sloterdijk 09:49No data—
Sun 30 AugSittard 12:15No data—