Train NS 5934 Roosendaal – Zwijndrecht

Roosendaal 10:38 → Zwijndrecht 11:12 Daily 0 h 34 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht at 11:23 0 min

  1. Roosendaal10:38
  2. Oudenbosch10:44
  3. Zevenbergen10:50
  4. Lage Zwaluwe10:55
  5. Dordrecht Zuid11:03
  6. Dordrecht11:07
  7. Zwijndrecht11:12

Next service: tomorrow 10:38 from Roosendaal · Sun 8 Nov

Next departure 10:38 tomorrow · Roosendaal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 8 full · 1 partial · 13 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 11 full · 1 partial · 43 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: +3 min

Last 30 days

Arrival delay at Zwijndrecht, 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 +4 min · last fix heading to Dordrecht Zuid +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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
10:38on time on time
10:44≈ on time ≈ on time
10:50≈ on time ≈ +1 min
10:55≈ on time ≈ +1 min
11:03≈ on time ≈ +2 min
11:07 / 11:09≈ on time ≈ +2 min
11:12on 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
Sat 7 NovDordrecht 11:23Partial coverage0 min—
Fri 6 NovDordrecht Zuid 11:17No data—
Thu 5 NovDordrecht Zuid 11:19No data—
Wed 4 NovDordrecht Zuid 11:19+2 min+2 min
Tue 3 NovDordrecht Zuid 11:17No data—
Mon 2 NovDordrecht Zuid 11:17No data—
Fri 30 OctDordrecht Zuid 11:180 min—
Thu 29 OctDordrecht Zuid 11:17No data—
Wed 28 OctDordrecht Zuid 11:170 min—
Tue 27 OctDordrecht Zuid 11:170 min—
Mon 26 OctDordrecht Zuid 11:17No data—
Fri 23 OctDordrecht Zuid 11:17No data—
Thu 22 OctDordrecht Zuid 11:17No data—
Wed 21 OctDordrecht Zuid 11:180 min—
Tue 20 OctDordrecht Zuid 11:170 min—
Mon 19 OctDordrecht Zuid 11:17No data—
Fri 16 OctDordrecht Zuid 11:170 min—
Thu 15 OctDordrecht Zuid 11:18No data—
Wed 14 OctDordrecht Zuid 11:17No data—
Tue 13 OctDordrecht Zuid 11:17No data—
Mon 12 OctDordrecht Zuid 11:17No data—
Fri 9 OctDordrecht Zuid 11:21+4 min+4 min
Thu 8 OctDordrecht Zuid 11:170 min—
Wed 7 OctZevenbergen 12:020 min—
Tue 6 OctDordrecht Zuid 11:170 min—
Mon 5 OctDordrecht Zuid 11:17No data—
Fri 2 OctDordrecht Zuid 11:17No data—
Thu 1 OctDordrecht Zuid 11:17No data—
Wed 30 SeptDordrecht Zuid 11:18No data—
Tue 29 SeptDordrecht Zuid 11:17No data—