Train NS 3567 Dordrecht – Venlo

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

It has not run yet today

Last recorded run: Wednesday 4 November +11 min

Next service: today 17:04 from Dordrecht · Thu 5 Nov

Next departure 17:04 today · Dordrecht
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 13 full · 6 partial · 10 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 14 full · 7 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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 +44 min · last fix heading to Dordrecht +44 min
  • Wed 4 Nov Max en route +12 min · last fix heading to Dordrecht +11 min
  • Fri 23 Oct Max en route +5 min · last fix heading to 's-Hertogenbosch +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 5% · 1

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 67% W n=3
  • 100% T n=2
  • 33% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
17:04on time on time
17:15≈ on time ≈ on time
17:18 / 17:22≈ on time ≈ on time
17:27≈ on time ≈ on time
17:34≈ on time ≈ +1 min
17:41 / 17:43≈ on time ≈ +1 min
17:46≈ on time ≈ +1 min
17:55 / 17:57≈ on time ≈ +1 min
18:14 / 18:15≈ on time ≈ +1 min
18:22 / 18:26≈ on time ≈ +2 min
18:31 / 18:32≈ on time ≈ +2 min
18:48 / 18:54≈ on time ≈ +2 min
19:21 / 19:24≈ on time ≈ +3 min
19:45 / 19:49≈ on time ≈ +3 min
19:58 / 19:59≈ on time ≈ +4 min
20:06≈ on time ≈ +4 min
20:17≈ on time ≈ +4 min
20:25≈ on time ≈ +4 min
20:28on time +4 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
Wed 4 NovDordrecht 20:49Partial coverage+11 min+12 min
Tue 3 NovDordrecht 20:30No data—
Mon 2 NovLeiden Centraal 19:29Partial coverage0 min—
Sun 1 Nov's-Hertogenbosch 19:440 min—
Sat 31 Oct's-Hertogenbosch 19:380 min—
Fri 30 OctDordrecht 19:520 min—
Thu 29 OctDordrecht 20:30Partial coverage0 min—
Wed 28 OctDordrecht 20:290 min—
Tue 27 OctDordrecht 20:300 min—
Mon 26 OctLeiden Centraal 18:11No data—
Sun 25 OctHorst-Sevenum 20:53No data—
Sat 24 OctBlerick 20:400 min—
Fri 23 Oct's-Hertogenbosch 20:34+5 min+5 min
Thu 22 OctAmsterdam Bijlmer ArenA 19:54No data—
Wed 21 OctDordrecht 20:30No data—
Tue 20 OctDordrecht 20:300 min—
Mon 19 OctAmsterdam Bijlmer ArenA 18:46Partial coverage0 min—
Sun 18 OctBlerick 20:41+2 min+4 min
Sat 17 OctBlerick 20:39No data—
Fri 16 OctEindhoven Centraal 20:30No data—
Thu 15 OctDordrecht 20:38No data—
Wed 14 Oct's-Hertogenbosch 20:29No data—
Tue 13 OctDordrecht 20:30No data—
Mon 12 OctDordrecht 20:29Partial coverage0 min—
Sun 11 OctBlerick 20:400 min—
Sat 10 OctBlerick 20:410 min—
Fri 9 OctDordrecht 21:13+44 min+44 min
Thu 8 OctRotterdam Centraal 07:370 min—
Wed 7 OctDordrecht 20:38Partial coverage0 min—
Tue 6 OctDordrecht 20:29Partial coverage0 min—