Train NS 3575 Dordrecht – Venlo

Dordrecht 19:04 → Venlo 22:28 Daily 3 h 24 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 22:29 +1 min

  1. Dordrecht19:04
  2. Schiedam Centrum19:27
  3. Den Haag Laan v NOI19:46
  4. Amsterdam Zuid20:22
  5. 's-Hertogenbosch21:21
  6. Deurne22:06
  7. Venlo22:28

Next service: tomorrow 19:04 from Dordrecht · Fri 13 Nov

Next departure 19:04 tomorrow · Dordrecht
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 29 full · 0 partial · 30 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 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 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Dordrecht +4 min
  • Sat 31 Oct Max en route +4 min · last fix heading to 's-Hertogenbosch +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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:04on time on time
19:15≈ on time ≈ on time
19:18 / 19:22≈ on time ≈ on time
19:27≈ on time ≈ on time
19:34≈ on time ≈ on time
19:41 / 19:43≈ on time ≈ on time
19:46≈ on time ≈ +1 min
19:55 / 20:00≈ on time ≈ +1 min
20:15 / 20:16≈ on time ≈ +1 min
20:22 / 20:26≈ on time ≈ +1 min
20:31 / 20:32≈ on time ≈ +1 min
20:48 / 20:54≈ on time ≈ +1 min
21:21 / 21:24≈ on time ≈ +2 min
21:45 / 21:49≈ on time ≈ +2 min
21:58 / 21:59≈ on time ≈ +2 min
22:06≈ on time ≈ +2 min
22:17≈ on time ≈ +2 min
22:25≈ on time ≈ +2 min
22: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
Thu 12 Nov— 22:29+1 min+1 min
Wed 11 Nov— 22:290 min—
Tue 10 Nov— 22:290 min—
Mon 9 Nov— 22:290 min—
Sun 8 NovBlerick 22:390 min—
Sat 7 NovBlerick 22:390 min—
Fri 6 Nov— 22:290 min—
Thu 5 Nov— 22:290 min—
Wed 4 Nov— 22:290 min—
Tue 3 Nov— 22:290 min—
Sun 1 Nov's-Hertogenbosch 21:440 min—
Sat 31 Oct's-Hertogenbosch 22:11+4 min+4 min
Fri 30 Oct— 22:05No data—
Thu 29 Oct— 22:06+1 min—
Wed 28 Oct— 20:070 min—
Tue 27 Oct— 23:18No data—
Mon 26 OctDelft 22:30No data—
Sun 25 OctBlerick 22:39No data—
Sat 24 OctBlerick 22:40No data—
Fri 23 OctDordrecht 21:51+4 min+4 min
Thu 22 Oct— 22:31No data—
Wed 21 Oct— 22:300 min—
Tue 20 Oct— 22:400 min—
Mon 19 Oct— 22:300 min—
Sun 18 OctBlerick 22:390 min+2 min
Sat 17 OctBlerick 22:390 min—
Fri 16 OctDordrecht 22:300 min—
Thu 15 Oct— 22:29No data—
Wed 14 OctDordrecht 22:29No data—
Tue 13 Oct— 22:30No data—