Train NS 5961 Dordrecht – Roosendaal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:53 from Dordrecht · Thu 5 Nov

Next departure 16:53 today · Dordrecht
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 11 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 40 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 Roosendaal, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +4 min · last fix heading to Oudenbosch +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

  • 100% M n=2
  • 100% T n=3
  • 100% W n=4
  • 0% T n=1
  • 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, 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
16:53on time on time
16:56— —
17:04— —
17:10— —
17:16— —
17:23— —

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 4 NovOudenbosch 17:29Partial coverage0 min—
Tue 3 NovOudenbosch 17:29No data—
Mon 2 NovOudenbosch 17:29No data—
Fri 30 OctOudenbosch 17:35Partial coverage0 min—
Thu 29 OctOudenbosch 17:30No data—
Wed 28 OctOudenbosch 17:30No data—
Tue 27 OctOudenbosch 17:30Partial coverage0 min—
Mon 26 OctOudenbosch 17:30No data—
Fri 23 OctOudenbosch 17:34No data—
Thu 22 OctOudenbosch 17:30No data—
Wed 21 OctOudenbosch 17:31Partial coverage0 min—
Tue 20 OctOudenbosch 17:30Partial coverage0 min—
Mon 19 OctOudenbosch 17:30No data—
Fri 16 OctOudenbosch 17:31No data—
Thu 15 OctOudenbosch 17:30No data—
Wed 14 OctOudenbosch 17:30Partial coverage0 min—
Tue 13 OctOudenbosch 17:30No data—
Mon 12 OctOudenbosch 17:30Partial coverage0 min—
Fri 9 OctOudenbosch 17:30Partial coverage0 min—
Thu 8 OctOudenbosch 17:31Partial coverage+4 min+4 min
Wed 7 OctOudenbosch 17:30Partial coverage0 min—
Tue 6 OctOudenbosch 17:30Partial coverage0 min—
Mon 5 OctOudenbosch 17:27Partial coverage0 min—
Fri 2 OctOudenbosch 17:30No data—
Thu 1 OctOudenbosch 17:30No data—
Wed 30 SeptOudenbosch 17:30No data—
Tue 29 SeptOudenbosch 17:30No data—
Mon 28 SeptOudenbosch 17:30No data—
Fri 25 SeptOudenbosch 17:30No data—
Thu 24 SeptOudenbosch 17:29No data—