Train NS 3571 Dordrecht – Venlo

Dordrecht 18:09 → Venlo 21:28 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 18:09 from Dordrecht · Sun 15 Nov

Next departure 18:09 today · Dordrecht
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 17 full · 4 partial · 8 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 25 full · 7 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Venlo, 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 13 Nov Max en route +13 min · last fix heading to Dordrecht +13 min
  • Fri 23 Oct Max en route +8 min · last fix heading to Dordrecht +7 min
  • Wed 7 Oct Max en route +6 min · last fix heading to Dordrecht +6 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 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 80% W n=5
  • 100% T n=4
  • 67% F n=6
  • 100% S n=6
  • 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
18:09on time on time
18:20≈ on time ≈ on time
18:23 / 18:26≈ on time ≈ on time
18:31≈ on time ≈ on time
18:38≈ on time ≈ on time
18:45 / 18:47≈ on time ≈ on time
18:50≈ on time ≈ +1 min
18:59 / 19:00≈ on time ≈ +1 min
19:15 / 19:16≈ on time ≈ +1 min
19:23 / 19:26≈ on time ≈ +1 min
19:31 / 19:32≈ on time ≈ +1 min
19:48 / 19:54≈ on time ≈ +1 min
20:21 / 20:24≈ on time ≈ +2 min
20:44 / 20:49≈ on time ≈ +2 min
20:58 / 20:59≈ on time ≈ +2 min
21:06≈ on time ≈ +2 min
21:17≈ on time ≈ +2 min
21:25≈ on time ≈ +2 min
21:28on 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 NovBlerick 21:39Partial coverage0 min—
Fri 13 NovDordrecht 21:54Partial coverage+13 min+13 min
Thu 12 NovDordrecht 21:29+1 min+3 min
Wed 11 NovDordrecht 21:290 min—
Tue 10 NovDordrecht 21:290 min—
Mon 9 NovDordrecht 21:29+2 min+2 min
Sun 8 NovBlerick 21:390 min—
Sat 7 NovBlerick 21:390 min—
Fri 6 NovDordrecht 21:29Partial coverage+1 min+2 min
Thu 5 NovDordrecht 21:29No data—
Wed 4 NovDordrecht 21:34+3 min+5 min
Tue 3 NovDordrecht 21:29No data—
Mon 2 NovDordrecht 18:18No data—
Sun 1 Nov's-Hertogenbosch 20:44+1 min+2 min
Sat 31 Oct's-Hertogenbosch 20:390 min—
Fri 30 OctDordrecht 21:050 min—
Thu 29 Oct— 21:070 min—
Wed 28 OctDordrecht 18:560 min—
Tue 27 OctDordrecht 21:30No data—
Mon 26 OctDordrecht 20:500 min—
Sun 25 OctBlerick 21:43No data—
Sat 24 OctBlerick 22:030 min—
Fri 23 OctDordrecht 21:41+7 min+8 min
Thu 22 OctDordrecht 21:30No data—
Wed 21 OctDordrecht 21:30No data—
Tue 20 OctDordrecht 21:41No data—
Mon 19 OctDordrecht 21:290 min—
Sun 18 OctBlerick 21:40Partial coverage+1 min—
Sat 17 OctBlerick 21:400 min—
Fri 16 OctUtrecht Centraal 21:30Partial coverage0 min—