Train NS 5987 Dordrecht – Roosendaal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:23 from Dordrecht · Fri 6 Nov

Full trip card
Next departure 23:23 today · Dordrecht
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 14 full · 5 partial · 9 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 17 full · 5 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 8 Oct Max en route +14 min · last fix heading to — +14 min
  • Mon 2 Nov Max en route +3 min · last fix heading to — +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 9% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=2
  • 50% T n=2
  • 67% F n=3
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

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