Train NS 5963 Dordrecht – Roosendaal

Dordrecht 17:23 → Roosendaal 17:53 Daily 0 h 30 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 17:23 from Dordrecht · Sat 7 Nov

Next departure 17:23 today · Dordrecht
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 16 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 1 full · 16 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Roosendaal, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=1
  • 100% F n=3
  • 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, 17 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
17:23on time on time
17:26— —
17:34— —
17:40— —
17:46— —
17:53— —

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 NovOudenbosch 17:59Partial coverage+1 min+3 min
Thu 5 NovOudenbosch 17:59No data—
Wed 4 NovOudenbosch 17:59Partial coverage0 min—
Tue 3 NovOudenbosch 17:59No data—
Mon 2 NovOudenbosch 17:59No data—
Sun 1 NovOudenbosch 18:01Partial coverage0 min—
Sat 31 OctOudenbosch 18:01Partial coverage0 min—
Fri 30 OctOudenbosch 18:000 min—
Thu 29 OctOudenbosch 18:00No data—
Wed 28 OctOudenbosch 18:05Partial coverage0 min—
Tue 27 OctOudenbosch 18:00No data—
Mon 26 OctOudenbosch 18:00Partial coverage+1 min—
Sun 25 OctOudenbosch 18:01No data—
Sat 24 OctOudenbosch 18:02Partial coverage0 min—
Fri 23 OctOudenbosch 18:01No data—
Thu 22 OctOudenbosch 17:55No data—
Wed 21 OctOudenbosch 18:00No data—
Tue 20 OctOudenbosch 18:05No data—
Mon 19 OctOudenbosch 18:00No data—
Sun 18 OctOudenbosch 18:02Partial coverage0 min—
Sat 17 OctOudenbosch 18:01No data—
Fri 16 OctOudenbosch 18:06No data—
Thu 15 OctOudenbosch 18:00No data—
Wed 14 OctOudenbosch 18:01No data—
Tue 13 OctOudenbosch 18:00No data—
Mon 12 OctOudenbosch 18:00Partial coverage0 min—
Sun 11 OctOudenbosch 18:01Partial coverage0 min—
Sat 10 OctOudenbosch 18:05Partial coverage0 min—
Fri 9 OctOudenbosch 18:00Partial coverage0 min—
Thu 8 OctOudenbosch 17:58Partial coverage0 min—