Train NS 5951 Zwijndrecht – Roosendaal

Zwijndrecht 14:18 → Roosendaal 14:53 Daily 0 h 35 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 14:18 from Zwijndrecht · Sun 8 Nov

Next departure 14:18 today · Zwijndrecht
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 12 full · 1 partial · 16 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 57 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

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=1
  • 100% T n=3
  • 100% W n=4
  • 100% T n=1
  • 100% F n=2
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
14:18on time on time
14:22 / 14:23≈ on time ≈ on time
14:26≈ on time ≈ on time
14:34≈ on time ≈ on time
14:40≈ on time ≈ on time
14:46≈ on time ≈ on time
14:53on time on time

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