Train NS 5975 Dordrecht – Roosendaal

Dordrecht 20:23 → Roosendaal 20:53 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 20:23 from Dordrecht · Thu 5 Nov

Next departure 20:23 today · Dordrecht
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 8 full · 5 partial · 14 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 31 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

Worst days

  • Thu 29 Oct Max en route +14 min · last fix heading to — +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
20:23on time on time
20:26≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:40≈ on time ≈ +2 min
20:46≈ on time ≈ +2 min
20:53on time +2 min

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 Nov— 20:540 min—
Tue 3 Nov— 20:54No data—
Sun 1 NovOudenbosch 20:59Partial coverage0 min—
Sat 31 OctOudenbosch 21:00Partial coverage0 min—
Fri 30 Oct— 20:54No data—
Thu 29 Oct— 21:05+14 min+14 min
Wed 28 Oct— 20:540 min—
Tue 27 Oct— 21:010 min—
Mon 26 Oct— 21:05No data—
Sun 25 OctOudenbosch 21:07No data—
Sat 24 OctOudenbosch 21:02No data—
Fri 23 Oct— 20:550 min—
Thu 22 Oct— 20:55No data—
Wed 21 Oct— 20:55No data—
Tue 20 Oct— 20:54No data—
Mon 19 Oct— 20:55No data—
Sun 18 OctOudenbosch 21:01Partial coverage0 min—
Sat 17 OctOudenbosch 21:00No data—
Fri 16 Oct— 20:540 min—
Thu 15 Oct— 20:57No data—
Wed 14 Oct— 20:54No data—
Tue 13 Oct— 20:55No data—
Mon 12 Oct— 20:54No data—
Sun 11 OctOudenbosch 21:01Partial coverage0 min—
Sat 10 OctOudenbosch 21:00Partial coverage0 min—
Fri 9 Oct— 20:540 min—
Wed 7 Oct— 20:530 min—
Tue 6 Oct— 20:55+1 min+1 min
Mon 5 Oct— 20:540 min—
Sun 4 OctOudenbosch 20:31No data—