Train NS 5988 Roosendaal – Dordrecht

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

✓ Today’s run finished

Today, last fix heading to — at 00:39 No data

  1. Roosendaal00:08
  2. Oudenbosch00:14
  3. Zevenbergen00:20
  4. Lage Zwaluwe00:25
  5. Dordrecht Zuid00:33
  6. Dordrecht00:37

Next service: tomorrow 00:08 from Roosendaal · Sat 7 Nov

Next departure 00:08 tomorrow · Roosendaal
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 21 full · 4 partial · 1 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 23 full · 4 partial · 9 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: +2 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

  • Sat 24 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 75% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 27 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
00:08on time on time
00:14≈ on time ≈ on time
00:20≈ on time ≈ +1 min
00:25≈ on time ≈ +1 min
00:33≈ on time ≈ +2 min
00:37on 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
Fri 6 Nov— 00:39No data—
Thu 5 Nov— 00:390 min—
Wed 4 Nov— 00:430 min—
Tue 3 Nov— 00:440 min—
Sun 1 NovDordrecht Zuid 00:47Partial coverage0 min—
Sat 31 Oct— 00:410 min—
Fri 30 Oct— 00:43+3 min+3 min
Thu 29 Oct— 00:380 min—
Wed 28 Oct— 00:410 min—
Tue 27 Oct— 00:380 min—
Sun 25 OctDordrecht Zuid 00:47Partial coverage0 min—
Sat 24 Oct— 00:45+3 min+3 min
Fri 23 Oct— 00:490 min—
Thu 22 Oct— 00:500 min—
Wed 21 Oct— 00:390 min—
Tue 20 Oct— 00:210 min—
Sun 18 OctDordrecht Zuid 00:47Partial coverage0 min—
Sat 17 OctLage Zwaluwe 00:39+1 min—
Fri 16 Oct— 00:380 min—
Thu 15 Oct— 00:380 min—
Wed 14 Oct— 00:410 min—
Tue 13 Oct— 00:380 min—
Sun 11 OctDordrecht Zuid 00:47Partial coverage0 min+2 min
Sat 10 Oct— 00:380 min—
Fri 9 Oct— 00:43+2 min+3 min
Thu 8 Oct— 00:39+1 min—
Wed 7 Oct— 00:390 min—
Tue 6 OctRoosendaal 00:430 min—
Sun 4 OctDordrecht Zuid 00:55No data—
Mon 28 SeptDordrecht Zuid 01:08No data—