Train NS 5944 Roosendaal – Dordrecht

Roosendaal 13:08 → Dordrecht 13:37 Daily 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht Zuid at 13:47 No data

  1. Roosendaal13:08
  2. Oudenbosch13:14
  3. Zevenbergen13:20
  4. Lage Zwaluwe13:25
  5. Dordrecht Zuid13:33
  6. Dordrecht13:37

Next service: tomorrow 13:08 from Roosendaal · Sat 7 Nov

Next departure 13:08 tomorrow · Roosendaal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 16 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 0 full · 16 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
13:08on time on time
13:14— —
13:20— —
13:25— —
13:33— —
13:37— —

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
Fri 6 NovDordrecht Zuid 13:47No data—
Thu 5 NovDordrecht Zuid 13:54No data—
Wed 4 NovDordrecht Zuid 13:47Partial coverage0 min—
Tue 3 NovDordrecht Zuid 13:48Partial coverage0 min—
Mon 2 NovDordrecht Zuid 13:47No data—
Sun 1 NovDordrecht Zuid 13:48Partial coverage+1 min—
Sat 31 OctDordrecht Zuid 13:47Partial coverage0 min—
Fri 30 OctDordrecht Zuid 13:47Partial coverage0 min—
Thu 29 OctDordrecht Zuid 13:47Partial coverage0 min—
Wed 28 OctDordrecht Zuid 13:49No data—
Tue 27 OctDordrecht Zuid 13:47No data—
Mon 26 OctDordrecht Zuid 13:47No data—
Sun 25 OctDordrecht Zuid 13:48No data—
Sat 24 OctDordrecht Zuid 13:47Partial coverage0 min—
Fri 23 OctDordrecht Zuid 13:47No data—
Thu 22 OctDordrecht Zuid 13:47No data—
Wed 21 OctDordrecht Zuid 13:51Partial coverage0 min—
Tue 20 OctDordrecht Zuid 13:47No data—
Mon 19 OctZevenbergen 13:35No data—
Sun 18 OctDordrecht Zuid 13:47Partial coverage0 min—
Sat 17 OctDordrecht Zuid 13:50No data—
Fri 16 OctDordrecht Zuid 13:47No data—
Thu 15 OctDordrecht Zuid 13:47No data—
Wed 14 OctDordrecht Zuid 13:48Partial coverage0 min—
Tue 13 OctDordrecht Zuid 13:50No data—
Mon 12 OctDordrecht Zuid 13:47No data—
Sun 11 OctDordrecht Zuid 13:47Partial coverage0 min—
Sat 10 OctDordrecht Zuid 13:47Partial coverage0 min—
Fri 9 OctDordrecht Zuid 13:47Partial coverage0 min—
Thu 8 OctDordrecht Zuid 13:47Partial coverage0 min—