Train NS 5972 Roosendaal – Dordrecht

Roosendaal 20:08 → Dordrecht 20:37 Daily 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 20:39 No data

  1. Roosendaal20:08
  2. Oudenbosch20:14
  3. Zevenbergen20:20
  4. Lage Zwaluwe20:25
  5. Dordrecht Zuid20:33
  6. Dordrecht20:37

Next service: tomorrow 20:08 from Roosendaal · Fri 6 Nov

Next departure 20:08 tomorrow · Roosendaal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 8 full · 5 partial · 14 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 10 full · 5 partial · 33 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: +6 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

  • Thu 29 Oct Max en route +12 min · last fix heading to — +12 min
  • Fri 16 Oct Max en route +7 min · last fix heading to — +7 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 87% · 13
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=3
  • 0% T n=1
  • 67% 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:08on time on time
20:14≈ on time ≈ +2 min
20:20≈ on time ≈ +3 min
20:25≈ on time ≈ +4 min
20:33≈ on time ≈ +6 min
20:37on time +7 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
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:39+1 min+1 min
Tue 3 Nov— 20:39No data—
Sun 1 NovDordrecht Zuid 20:49Partial coverage+2 min+2 min
Sat 31 OctDordrecht Zuid 20:47Partial coverage0 min—
Thu 29 Oct— 21:01+12 min+12 min
Wed 28 Oct— 20:390 min—
Tue 27 Oct— 20:51No data—
Mon 26 Oct— 20:48No data—
Sun 25 OctDordrecht Zuid 20:47No data—
Sat 24 OctDordrecht Zuid 20:48No data—
Fri 23 Oct— 20:380 min—
Thu 22 Oct— 20:39No data—
Wed 21 Oct— 20:38No data—
Tue 20 Oct— 20:20No data—
Mon 19 Oct— 20:21No data—
Sun 18 OctDordrecht Zuid 20:47Partial coverage0 min—
Sat 17 OctDordrecht Zuid 20:47No data—
Fri 16 Oct— 20:51+7 min+7 min
Thu 15 Oct— 20:38No data—
Wed 14 Oct— 20:43No data—
Tue 13 Oct— 20:39No data—
Mon 12 Oct— 20:380 min—
Sun 11 OctDordrecht Zuid 20:47Partial coverage0 min—
Sat 10 OctDordrecht Zuid 20:47Partial coverage0 min—
Fri 9 Oct— 20:380 min—
Wed 7 Oct— 20:380 min—
Tue 6 Oct— 20:380 min—
Mon 5 Oct— 20:380 min—
Sun 4 OctDordrecht Zuid 20:47No data—