Train NS 5922 Roosendaal – Dordrecht

Roosendaal 07:38 → Dordrecht 08:07 Daily 0 h 29 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht Zuid at 08:17 No data

  1. Roosendaal07:38
  2. Oudenbosch07:44
  3. Zevenbergen07:50
  4. Lage Zwaluwe07:55
  5. Dordrecht Zuid08:03
  6. Dordrecht08:07

Next service: tomorrow 07:38 from Roosendaal · Sat 7 Nov

Next departure 07:38 tomorrow · Roosendaal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 0 full · 16 partial · 6 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 0 full · 18 partial · 36 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 Dordrecht, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=2
  • 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, 18 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:38on time on time
07:44— —
07:50— —
07:55— —
08:03— —
08:07— —

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 NovDordrecht Zuid 08:17No data—
Thu 5 NovDordrecht Zuid 08:29No data—
Wed 4 NovDordrecht Zuid 08:18Partial coverage+1 min+1 min
Tue 3 NovDordrecht Zuid 08:19Partial coverage0 min—
Mon 2 NovDordrecht Zuid 08:19Partial coverage0 min—
Fri 30 OctDordrecht Zuid 08:18Partial coverage0 min—
Thu 29 OctDordrecht Zuid 08:18Partial coverage0 min—
Wed 28 OctDordrecht Zuid 08:17Partial coverage0 min—
Tue 27 OctDordrecht Zuid 08:17Partial coverage0 min—
Mon 26 OctDordrecht Zuid 08:17Partial coverage0 min—
Fri 23 OctDordrecht Zuid 08:18Partial coverage0 min—
Thu 22 OctDordrecht Zuid 08:17No data—
Wed 21 OctDordrecht Zuid 08:17Partial coverage0 min—
Tue 20 OctDordrecht Zuid 08:17Partial coverage0 min—
Mon 19 OctDordrecht Zuid 08:17Partial coverage0 min—
Fri 16 OctDordrecht Zuid 08:17Partial coverage0 min—
Thu 15 OctDordrecht Zuid 08:17No data—
Wed 14 OctDordrecht Zuid 08:18No data—
Tue 13 OctDordrecht Zuid 08:17Partial coverage0 min—
Mon 12 OctDordrecht Zuid 08:17No data—
Fri 9 OctDordrecht Zuid 08:17Partial coverage0 min—
Thu 8 OctDordrecht Zuid 08:18Partial coverage+1 min+1 min
Wed 7 OctDordrecht Zuid 08:17Partial coverage0 min—
Tue 6 OctDordrecht Zuid 08:18Partial coverage+1 min+1 min
Mon 5 OctDordrecht Zuid 08:19No data—
Fri 2 OctDordrecht Zuid 08:17No data—
Thu 1 OctDordrecht Zuid 08:18No data—
Wed 30 SeptDordrecht Zuid 08:22No data—
Tue 29 SeptDordrecht Zuid 08:17No data—
Mon 28 SeptDordrecht Zuid 08:18No data—