Train NS 5951 Dordrecht → Roosendaal

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

NS 5951 Dordrecht–Roosendaal: final delay under 3 min on 23 of its 23 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Roosendaal: 14:53. TrainsRadar data as of 22 Nov 2026, 14:38 (GMT+1).

Running now · updated 14:38

Heading to Roosendaal 0 min

Estimated arrival at Roosendaal 14:53

  1. Dordrecht14:23
  2. Dordrecht Zuid14:26
  3. Lage Zwaluwe14:34
  4. Zevenbergen14:40
  5. Oudenbosch14:46
  6. Roosendaal14:53

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 23 runs arrived on time.

On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 2 full · 21 partial · 7 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 2 full · 31 partial · 44 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 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

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

  • Early 0% · 0
  • On time 100% · 33
  • 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=6
  • 100% T n=3
  • 100% F n=4
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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