Train NS 5971 Dordrecht – Roosendaal

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 19:23 from Dordrecht · Tue 10 Nov

Next departure 19:23 today · Dordrecht
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 8 full · 5 partial · 15 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 33 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: +2 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
19:23on time on time
19:26≈ on time ≈ on time
19:34≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:46≈ on time ≈ +1 min
19: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
Mon 9 Nov— 19:540 min—
Sun 8 NovOudenbosch 19:59+1 min—
Sat 7 NovOudenbosch 20:02+3 min+3 min
Fri 6 Nov— 19:59+2 min+2 min
Thu 5 Nov— 19:54No data—
Wed 4 Nov— 19:540 min—
Tue 3 Nov— 19:54No data—
Mon 2 Nov— 19:540 min—
Sun 1 NovOudenbosch 19:59Partial coverage0 min—
Sat 31 OctOudenbosch 20:01Partial coverage0 min—
Thu 29 Oct— 20:34No data—
Wed 28 Oct— 19:540 min—
Tue 27 Oct— 19:55No data—
Mon 26 OctOudenbosch 19:57No data—
Sun 25 OctOudenbosch 20:01No data—
Sat 24 OctOudenbosch 20:01No data—
Fri 23 OctDordrecht Zuid 19:56Partial coverage+1 min+1 min
Thu 22 Oct— 19:55No data—
Wed 21 Oct— 19:55No data—
Tue 20 Oct— 19:35No data—
Mon 19 Oct— 19:53No data—
Sun 18 OctOudenbosch 20:01Partial coverage0 min—
Sat 17 OctOudenbosch 20:01No data—
Fri 16 OctOudenbosch 20:00Partial coverage0 min—
Thu 15 Oct— 19:54No data—
Wed 14 OctOudenbosch 20:03No data—
Tue 13 Oct— 19:55No data—
Mon 12 Oct— 19:550 min—
Sun 11 OctOudenbosch 20:01Partial coverage0 min—
Sat 10 OctOudenbosch 20:01Partial coverage0 min—