Train NS 5914 Roosendaal – Zwijndrecht

Roosendaal 05:38 → Zwijndrecht 06:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 34 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Roosendaal05:38
  2. Oudenbosch05:44
  3. Zevenbergen05:50
  4. Lage Zwaluwe05:55
  5. Dordrecht Zuid06:03
  6. Dordrecht06:07
  7. Zwijndrecht06:12

Next service: Monday 05:38 from Roosendaal · Mon 9 Nov

Next departure 05:38 Monday · Roosendaal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 1 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 31 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: +1 min

Last 30 days

Arrival delay at Zwijndrecht, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 19 Oct Max en route +18 min · last fix heading to Dordrecht Zuid +18 min

Distribution · 90 days

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

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

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 100% W n=5
  • 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 (7 stops).

Last 90 days, 24 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
05:38on time on time
05:44≈ on time ≈ on time
05:50≈ on time ≈ +1 min
05:55≈ on time ≈ +1 min
06:03≈ on time ≈ +1 min
06:07 / 06:09≈ on time ≈ +2 min
06:12on time +2 min

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