Train NS 5923 Dordrecht – Roosendaal

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

✓ Today’s run finished

Today, last fix heading to Oudenbosch at 07:59 +1 min

  1. Dordrecht07:23
  2. Dordrecht Zuid07:26
  3. Lage Zwaluwe07:34
  4. Zevenbergen07:40
  5. Oudenbosch07:46
  6. Roosendaal07:53

Next service: tomorrow 07:23 from Dordrecht · Thu 12 Nov

Next departure 07:23 tomorrow · Dordrecht
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 2 full · 19 partial · 9 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 2 full · 26 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Sun 8 Nov Max en route +5 min · last fix heading to Oudenbosch +5 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Oudenbosch +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=5
  • 100% T n=2
  • 100% F n=4
  • 80% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 28 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
07:23on time on time
07:26— —
07:34— —
07:40— —
07:46— —
07:53— —

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
Wed 11 NovOudenbosch 07:59Partial coverage+1 min+2 min
Tue 10 NovOudenbosch 07:59Partial coverage0 min—
Mon 9 NovOudenbosch 08:09Partial coverage0 min—
Sun 8 NovOudenbosch 08:04+5 min+5 min
Sat 7 NovOudenbosch 08:05+5 min+5 min
Fri 6 NovOudenbosch 07:59No data—
Thu 5 NovOudenbosch 08:02No data—
Wed 4 NovOudenbosch 07:59Partial coverage0 min—
Tue 3 NovOudenbosch 08:02No data—
Mon 2 NovOudenbosch 08:02Partial coverage0 min—
Sun 1 NovOudenbosch 08:01Partial coverage0 min—
Sat 31 OctOudenbosch 08:00Partial coverage0 min—
Fri 30 OctOudenbosch 08:01Partial coverage0 min—
Thu 29 OctOudenbosch 08:01Partial coverage0 min—
Wed 28 OctOudenbosch 08:00Partial coverage0 min—
Tue 27 OctOudenbosch 08:01Partial coverage0 min—
Mon 26 OctOudenbosch 08:01Partial coverage0 min—
Sun 25 OctOudenbosch 08:01No data—
Sat 24 OctOudenbosch 08:01Partial coverage+1 min+1 min
Fri 23 OctOudenbosch 08:01Partial coverage0 min—
Thu 22 OctOudenbosch 08:01No data—
Wed 21 OctOudenbosch 08:01Partial coverage0 min—
Tue 20 OctOudenbosch 08:01Partial coverage0 min—
Mon 19 OctOudenbosch 08:01No data—
Sun 18 OctOudenbosch 08:02Partial coverage+2 min+8 min
Sat 17 OctOudenbosch 08:00Partial coverage0 min—
Fri 16 OctOudenbosch 08:01Partial coverage0 min—
Thu 15 OctOudenbosch 08:03No data—
Wed 14 OctOudenbosch 08:03No data—
Tue 13 OctOudenbosch 08:01No data—