Train NS 3574 Venlo – Dordrecht

Venlo 19:33 → Dordrecht 22:53 Daily 3 h 20 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 19:33 from Venlo · Sun 15 Nov

Next departure 19:33 today · Venlo
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 7 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 30 full · 2 partial · 23 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

Worst days

  • Fri 9 Oct Max en route +15 min · last fix heading to — +14 min
  • Wed 4 Nov Max en route +11 min · last fix heading to — +11 min
  • Mon 5 Oct Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 75% W n=4
  • 100% T n=5
  • 83% F n=6
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 32 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
19:33on time on time
19:36≈ on time ≈ on time
19:43≈ on time ≈ on time
19:54≈ on time ≈ on time
20:01≈ on time ≈ on time
20:11 / 20:16≈ on time ≈ on time
20:36 / 20:40≈ on time ≈ +1 min
21:06 / 21:11≈ on time ≈ +1 min
21:28≈ on time ≈ +1 min
21:34 / 21:37≈ on time ≈ +1 min
21:43 / 21:44≈ on time ≈ +1 min
22:00 / 22:02≈ on time ≈ +1 min
22:10 / 22:11≈ on time ≈ +2 min
22:14 / 22:15≈ on time ≈ +2 min
22:22≈ on time ≈ +2 min
22:30≈ on time ≈ +2 min
22:34 / 22:37≈ on time ≈ +2 min
22:40≈ on time ≈ +2 min
22:53on 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 14 NovRotterdam Blaak 22:54Partial coverage0 min—
Fri 13 Nov— 20:020 min—
Thu 12 Nov— 22:540 min—
Wed 11 Nov— 22:54+1 min+1 min
Tue 10 Nov— 22:54+1 min—
Mon 9 Nov— 22:540 min—
Sun 8 NovDelft 22:340 min+2 min
Sat 7 NovDelft 22:34+1 min—
Fri 6 Nov— 22:34+1 min+2 min
Thu 5 Nov— 22:540 min—
Wed 4 Nov— 20:29+11 min+11 min
Tue 3 Nov— 22:350 min—
Mon 2 Nov— 22:290 min+1 min
Sun 1 NovSchiphol Airport 21:590 min—
Sat 31 OctRotterdam Blaak 22:540 min—
Fri 30 Oct— 22:540 min—
Wed 28 Oct— 21:40No data—
Tue 27 Oct— 22:54No data—
Mon 26 OctDeurne 22:54No data—
Sun 25 OctRotterdam Blaak 22:54No data—
Sat 24 OctRotterdam Centraal 22:570 min—
Fri 23 Oct— 22:55+1 min+1 min
Thu 22 Oct— 22:550 min—
Wed 21 Oct— 22:55No data—
Tue 20 Oct— 22:540 min—
Mon 19 Oct— 22:54No data—
Sun 18 OctRotterdam Blaak 22:550 min—
Sat 17 OctRotterdam Blaak 22:59No data—
Fri 16 OctDeurne 22:54+1 min—
Thu 15 Oct— 23:080 min—