Train NS 5917 Dordrecht – Roosendaal

Dordrecht 05:53 → Roosendaal 06:23 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Oudenbosch at 06:29 +1 min

  1. Dordrecht05:53
  2. Dordrecht Zuid05:56
  3. Lage Zwaluwe06:04
  4. Zevenbergen06:10
  5. Oudenbosch06:16
  6. Roosendaal06:23

Next service: tomorrow 05:53 from Dordrecht · Fri 13 Nov

Next departure 05:53 tomorrow · Dordrecht
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 0 full · 21 partial · 1 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 1 full · 26 partial · 27 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: +1 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

  • Tue 13 Oct Max en route +4 min · last fix heading to Oudenbosch +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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
05:53on time on time
05:56— —
06:04— —
06:10— —
06:16— —
06:23— —

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 12 NovOudenbosch 06:29Partial coverage+1 min—
Wed 11 NovOudenbosch 06:29Partial coverage0 min—
Tue 10 NovOudenbosch 06:29Partial coverage0 min—
Mon 9 NovOudenbosch 06:32Partial coverage+2 min+2 min
Fri 6 NovOudenbosch 06:29No data—
Thu 5 NovOudenbosch 06:29Partial coverage0 min—
Wed 4 NovOudenbosch 06:29Partial coverage0 min—
Tue 3 NovOudenbosch 06:29Partial coverage0 min—
Mon 2 NovOudenbosch 06:34Partial coverage0 min—
Fri 30 OctOudenbosch 06:31Partial coverage0 min—
Thu 29 OctOudenbosch 06:31Partial coverage0 min—
Wed 28 OctOudenbosch 06:31Partial coverage0 min—
Tue 27 OctOudenbosch 06:36Partial coverage0 min—
Mon 26 OctOudenbosch 06:31Partial coverage0 min—
Fri 23 OctOudenbosch 06:31Partial coverage0 min—
Thu 22 OctOudenbosch 06:31Partial coverage0 min—
Wed 21 OctOudenbosch 06:30Partial coverage0 min—
Tue 20 OctOudenbosch 06:31Partial coverage0 min—
Mon 19 OctOudenbosch 06:31Partial coverage0 min—
Fri 16 OctOudenbosch 06:31Partial coverage0 min—
Thu 15 OctOudenbosch 06:31Partial coverage0 min—
Wed 14 OctOudenbosch 06:31Partial coverage+1 min—
Tue 13 OctOudenbosch 06:33Partial coverage+4 min+4 min
Mon 12 OctOudenbosch 06:31+1 min—
Fri 9 OctOudenbosch 06:32Partial coverage+1 min+1 min
Thu 8 OctOudenbosch 06:32Partial coverage0 min—
Wed 7 OctOudenbosch 06:31Partial coverage0 min—
Tue 6 OctOudenbosch 06:31Partial coverage0 min—
Mon 5 OctOudenbosch 06:31No data—
Fri 2 OctOudenbosch 06:31No data—