Train NS 5946 Roosendaal – Dordrecht

Roosendaal 13:38 → Dordrecht 14:07 Daily 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:38 from Roosendaal · Sat 7 Nov

Next departure 13:38 today · Roosendaal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 11 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 41 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

Worst days

  • Wed 7 Oct Max en route +8 min · last fix heading to Dordrecht Zuid +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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:38on time on time
13:44— —
13:50— —
13:55— —
14:03— —
14:07— —

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 14:17No data—
Thu 5 NovDordrecht Zuid 14:17No data—
Wed 4 NovDordrecht Zuid 14:17Partial coverage0 min—
Tue 3 NovDordrecht Zuid 14:19Partial coverage0 min—
Mon 2 NovDordrecht Zuid 14:17Partial coverage0 min—
Fri 30 OctDordrecht Zuid 14:17Partial coverage0 min—
Thu 29 OctDordrecht Zuid 14:17Partial coverage0 min—
Wed 28 OctDordrecht Zuid 14:17Partial coverage0 min—
Tue 27 OctDordrecht Zuid 14:17Partial coverage0 min—
Mon 26 OctDordrecht Zuid 14:17No data—
Fri 23 OctDordrecht Zuid 14:18No data—
Thu 22 OctDordrecht Zuid 14:17No data—
Wed 21 OctDordrecht Zuid 14:17Partial coverage0 min—
Tue 20 OctDordrecht Zuid 14:18Partial coverage0 min—
Mon 19 OctDordrecht Zuid 14:21No data—
Fri 16 OctDordrecht Zuid 14:17No data—
Thu 15 OctDordrecht Zuid 14:17No data—
Wed 14 OctDordrecht Zuid 14:17No data—
Tue 13 OctDordrecht Zuid 14:17No data—
Mon 12 OctDordrecht Zuid 14:17No data—
Fri 9 OctDordrecht Zuid 14:17Partial coverage0 min—
Thu 8 OctDordrecht Zuid 14:17Partial coverage0 min—
Wed 7 OctDordrecht Zuid 14:25Partial coverage+8 min+8 min
Tue 6 OctDordrecht Zuid 14:17Partial coverage0 min—
Mon 5 OctDordrecht Zuid 14:17No data—
Fri 2 OctDordrecht Zuid 14:17No data—
Thu 1 OctDordrecht Zuid 14:17No data—
Wed 30 SeptDordrecht Zuid 14:17No data—
Tue 29 SeptDordrecht Zuid 14:17No data—
Mon 28 SeptDordrecht Zuid 14:17No data—