Train NS 5939 Dordrecht – Roosendaal

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

✓ Today’s run finished

Today, last fix heading to Oudenbosch at 11:59 0 min

  1. Dordrecht11:23
  2. Dordrecht Zuid11:26
  3. Lage Zwaluwe11:34
  4. Zevenbergen11:40
  5. Oudenbosch11:46
  6. Roosendaal11:53

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

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

Worst days

  • Fri 9 Oct Max en route +3 min · last fix heading to Oudenbosch +3 min

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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 100% W n=5
  • 100% T n=1
  • 50% F n=2
  • 100% S n=4
  • 100% S n=4

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