Train NS 5970 Roosendaal – Dordrecht

Roosendaal 19:38 → Dordrecht 20:07 Daily 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 19:38 from Roosendaal · Sat 7 Nov

Next departure 19:38 today · Roosendaal
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 8 full · 0 partial · 12 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 11 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Dordrecht, in minutes. One bar per run.

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

Worst days

  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 9
  • 3–10 min 18% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 67% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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:38on time on time
19:44≈ on time ≈ +1 min
19:50≈ on time ≈ +2 min
19:55≈ on time ≈ +3 min
20:03≈ on time ≈ +5 min
20:07on time +5 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
Fri 6 Nov— 20:09+1 min—
Thu 5 Nov— 20:08No data—
Wed 4 Nov— 20:080 min—
Tue 3 Nov— 20:08No data—
Mon 2 Nov— 20:08No data—
Thu 29 Oct— 19:560 min—
Wed 28 Oct— 20:110 min—
Tue 27 Oct— 20:090 min—
Mon 26 Oct— 20:09No data—
Fri 23 Oct— 20:19+5 min+5 min
Thu 22 Oct— 20:09No data—
Wed 21 Oct— 20:09No data—
Tue 20 Oct— 20:08No data—
Mon 19 Oct— 20:06No data—
Fri 16 OctLage Zwaluwe 20:09No data—
Thu 15 Oct— 20:05No data—
Wed 14 OctOudenbosch 20:09No data—
Tue 13 Oct— 20:09No data—
Mon 12 Oct— 20:080 min—
Fri 9 Oct— 20:13+3 min+3 min
Thu 8 Oct— 20:080 min—
Tue 6 Oct— 20:080 min—
Mon 5 Oct— 20:19+5 min+5 min
Mon 17 AugOudenbosch 19:58No data—
Fri 14 AugDordrecht Zuid 20:18No data—
Thu 13 AugDordrecht Zuid 20:18No data—
Wed 12 AugDordrecht Zuid 20:18No data—
Tue 11 AugDordrecht Zuid 20:18No data—
Mon 10 AugLage Zwaluwe 20:09No data—