Train NS 5935 Dordrecht – Roosendaal

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

✓ Today’s run finished

Today, last fix heading to Oudenbosch at 10:59 No data

  1. Dordrecht10:23
  2. Dordrecht Zuid10:26
  3. Lage Zwaluwe10:34
  4. Zevenbergen10:40
  5. Oudenbosch10:46
  6. Roosendaal10:53

Next service: tomorrow 10:23 from Dordrecht · Sat 7 Nov

Next departure 10:23 tomorrow · Dordrecht
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 0 full · 19 partial · 11 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 1 full · 20 partial · 55 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

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