Train NS 2933 Enkhuizen – Roermond
It does not run today
Last recorded run: Sunday 15 November +1 min
Next service: tomorrow 08:39 from Enkhuizen · Fri 20 Nov
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 08:39 | on 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:30 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 15 Nov | Weert 11:33Partial coverage | +1 min | +1 min |
| Sat 14 Nov | Amsterdam Sloterdijk 09:48 | 0 min | — |
| Fri 13 Nov | Amsterdam Sloterdijk 09:49 | +1 min | — |
| Fri 6 Nov | Amsterdam Sloterdijk 09:48 | No data | — |
| Sun 1 Nov | Arnhem Centraal 11:04 | 0 min | — |
| Sat 31 Oct | Amsterdam Sloterdijk 09:48 | 0 min | — |
| Fri 30 Oct | Amsterdam Sloterdijk 09:48 | No data | — |
| Sun 25 Oct | Sittard 12:04 | No data | — |
| Sun 18 Oct | Sittard 12:05 | 0 min | — |
| Sat 17 Oct | Amsterdam Sloterdijk 09:48 | 0 min | — |
| Fri 16 Oct | Amsterdam Sloterdijk 09:49 | 0 min | — |
| Sun 11 Oct | Ede-Wageningen 10:50 | +1 min | +1 min |
| Sat 10 Oct | Amsterdam Sloterdijk 09:50 | +4 min | +4 min |
| Fri 9 Oct | Amsterdam Sloterdijk 09:50 | 0 min | +2 min |
| Mon 5 Oct | Sittard 12:07 | No data | — |
| Sun 4 Oct | Sittard 12:02 | No data | — |
| Fri 2 Oct | Amsterdam Sloterdijk 09:49 | No data | — |
| Sun 27 Sept | Sittard 12:01 | No data | — |
| Sat 26 Sept | Amsterdam Sloterdijk 09:48 | No data | — |
| Fri 25 Sept | Amsterdam Sloterdijk 09:48 | No data | — |
| Sun 20 Sept | Utrecht Centraal 10:23 | No data | — |
| Sat 19 Sept | Amsterdam Sloterdijk 09:48 | No data | — |
| Fri 18 Sept | Amsterdam Sloterdijk 09:49 | No data | — |
| Sun 13 Sept | Sittard 12:02 | No data | — |
| Sat 12 Sept | Amsterdam Sloterdijk 09:49 | No data | — |
| Fri 11 Sept | Amsterdam Sloterdijk 09:49 | No data | — |
| Sun 6 Sept | Weert 11:31 | No data | — |
| Sat 5 Sept | Amsterdam Sloterdijk 09:48 | No data | — |
| Fri 4 Sept | Amsterdam Sloterdijk 09:49 | No data | — |
| Sun 30 Aug | Sittard 12:15 | No data | — |