Train NS 5916 Roosendaal – Dordrecht

Roosendaal 06:08 → Dordrecht 06:37 Mon, Tue, Wed, Thu, Fri, Sat 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht Zuid at 06:48 +1 min

  1. Roosendaal06:08
  2. Oudenbosch06:14
  3. Zevenbergen06:20
  4. Lage Zwaluwe06:25
  5. Dordrecht Zuid06:33
  6. Dordrecht06:37

Next service: tomorrow 06:08 from Roosendaal · Thu 12 Nov

Next departure 06:08 tomorrow · Roosendaal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 2 full · 19 partial · 2 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 2 full · 24 partial · 28 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: +3 min

Last 30 days

Arrival delay at Dordrecht, 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 10 Nov Max en route +4 min · last fix heading to Dordrecht Zuid +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
06:08on time on time
06:14— —
06:20— —
06:25— —
06:33— —
06:37— —

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 NovDordrecht Zuid 06:48Partial coverage+1 min—
Tue 10 NovDordrecht Zuid 06:49Partial coverage+4 min+4 min
Mon 9 NovDordrecht Zuid 06:47Partial coverage0 min—
Sat 7 NovDordrecht 06:530 min—
Fri 6 NovDordrecht Zuid 06:52No data—
Thu 5 NovDordrecht Zuid 06:47Partial coverage0 min—
Wed 4 NovDordrecht Zuid 06:48Partial coverage0 min—
Tue 3 NovDordrecht Zuid 06:49Partial coverage+2 min+2 min
Mon 2 NovDordrecht Zuid 06:49No data—
Fri 30 OctDordrecht Zuid 06:48Partial coverage+2 min+2 min
Thu 29 OctDordrecht Zuid 06:47Partial coverage0 min—
Wed 28 OctDordrecht Zuid 06:47Partial coverage0 min—
Tue 27 OctDordrecht Zuid 06:480 min—
Mon 26 OctDordrecht Zuid 06:47Partial coverage0 min—
Fri 23 OctDordrecht Zuid 06:47Partial coverage0 min—
Thu 22 OctDordrecht Zuid 06:47Partial coverage0 min—
Wed 21 OctDordrecht Zuid 06:47Partial coverage0 min—
Tue 20 OctDordrecht Zuid 06:50Partial coverage+3 min+3 min
Mon 19 OctDordrecht Zuid 06:47Partial coverage0 min—
Fri 16 OctDordrecht Zuid 06:47Partial coverage0 min—
Thu 15 OctDordrecht Zuid 06:47Partial coverage0 min—
Wed 14 OctDordrecht Zuid 06:50Partial coverage+3 min+3 min
Tue 13 OctDordrecht Zuid 06:47Partial coverage0 min—
Mon 12 OctDordrecht Zuid 06:48Partial coverage+1 min+1 min
Fri 9 OctDordrecht Zuid 06:48Partial coverage+1 min—
Thu 8 OctDordrecht Zuid 06:47Partial coverage0 min—
Wed 7 OctDordrecht Zuid 06:47Partial coverage0 min—
Tue 6 OctDordrecht Zuid 06:48Partial coverage+1 min+1 min
Mon 5 OctDordrecht Zuid 06:48No data—
Fri 2 OctDordrecht Zuid 06:48No data—