Train NS 5934 Roosendaal – Dordrecht

Roosendaal 10:38 → Dordrecht 11:07 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

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

Next service: tomorrow 10:38 from Roosendaal · Thu 19 Nov

Next departure 10:38 tomorrow · Roosendaal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 4 full · 12 partial · 8 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 6 full · 15 partial · 34 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: +2 min

Last 30 days

Arrival delay at Dordrecht, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 10 Nov Max en route +8 min · last fix heading to Dordrecht Zuid +7 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Dordrecht Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 80% T n=5
  • 100% W n=6
  • 100% T n=2
  • 75% F n=4
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 21 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 ≈ +1 min
10:50≈ on time ≈ +1 min
10:55≈ on time ≈ +2 min
11:03≈ on time ≈ +2 min
11:07on time +3 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
Wed 18 NovDordrecht Zuid 11:17Partial coverage0 min—
Tue 17 NovDordrecht Zuid 11:17Partial coverage+1 min—
Mon 16 NovDordrecht Zuid 11:17Partial coverage0 min—
Fri 13 NovDordrecht Zuid 11:18+1 min—
Thu 12 NovDordrecht Zuid 11:14Partial coverage+1 min+1 min
Wed 11 NovDordrecht Zuid 11:18Partial coverage+1 min+1 min
Tue 10 NovDordrecht Zuid 11:24Partial coverage+7 min+8 min
Mon 9 NovDordrecht Zuid 11:17Partial coverage0 min—
Sun 8 NovDordrecht 11:230 min—
Sat 7 NovDordrecht 11:230 min—
Fri 6 NovDordrecht Zuid 11:17No data—
Thu 5 NovDordrecht Zuid 11:19No data—
Wed 4 NovDordrecht Zuid 11:19Partial coverage+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:17Partial coverage0 min—
Tue 27 OctDordrecht Zuid 11:17Partial coverage0 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:18Partial coverage0 min—
Tue 20 OctDordrecht Zuid 11:17Partial coverage0 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—