Train NS 5957 Dordrecht – Roosendaal

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

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

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

Next departure 15:53 today · Dordrecht
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 1 full · 9 partial · 11 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 1 full · 11 partial · 40 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: 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

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 100% · 12
  • 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=2
  • 100% W n=3
  • 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, 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
15:53on time on time
15:56— —
16:04— —
16:10— —
16:16— —
16: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 16:34Partial coverage+2 min+3 min
Tue 3 NovOudenbosch 16:29Partial coverage0 min—
Mon 2 NovOudenbosch 16:29Partial coverage0 min—
Fri 30 OctOudenbosch 16:310 min—
Thu 29 OctOudenbosch 16:31Partial coverage0 min—
Wed 28 OctOudenbosch 16:31Partial coverage0 min—
Tue 27 OctOudenbosch 16:36No data—
Mon 26 OctOudenbosch 16:31No data—
Fri 23 OctOudenbosch 16:31No data—
Thu 22 OctOudenbosch 16:31No data—
Wed 21 OctOudenbosch 16:31No data—
Tue 20 OctOudenbosch 16:31No data—
Mon 19 OctOudenbosch 16:32No data—
Fri 16 OctOudenbosch 16:31No data—
Thu 15 OctOudenbosch 16:31No data—
Wed 14 OctOudenbosch 16:30No data—
Tue 13 OctOudenbosch 16:31No data—
Mon 12 OctOudenbosch 16:36Partial coverage0 min—
Fri 9 OctOudenbosch 16:30Partial coverage0 min—
Thu 8 OctOudenbosch 16:31Partial coverage0 min—
Wed 7 OctOudenbosch 16:31Partial coverage0 min—
Tue 6 OctOudenbosch 16:31Partial coverage0 min—
Mon 5 OctOudenbosch 16:32Partial coverage+1 min+2 min
Fri 2 OctOudenbosch 16:32No data—
Thu 1 OctOudenbosch 16:31No data—
Wed 30 SeptOudenbosch 16:31No data—
Tue 29 SeptOudenbosch 16:31No data—
Mon 28 SeptOudenbosch 16:33No data—
Fri 25 SeptOudenbosch 16:31No data—
Thu 24 SeptOudenbosch 16:31No data—