Train NS 3585 Dordrecht – Venlo

Dordrecht 21:39 → Venlo 00:58 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:39 from Dordrecht · Thu 5 Nov

Next departure 21:39 today · Dordrecht
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 2 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 27 full · 1 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 23 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
21:39on time on time
21:50≈ on time ≈ on time
21:53 / 21:56≈ on time ≈ on time
22:01≈ on time ≈ on time
22:08≈ on time ≈ on time
22:15 / 22:17≈ on time ≈ on time
22:20≈ on time ≈ on time
22:29 / 22:30≈ on time ≈ on time
22:45 / 22:46≈ on time ≈ on time
22:53 / 22:56≈ on time ≈ on time
23:02≈ on time ≈ on time
23:18 / 23:24≈ on time ≈ on time
23:51 / 23:54≈ on time ≈ on time
00:14 / 00:19≈ on time ≈ on time
00:28 / 00:29≈ on time ≈ on time
00:36≈ on time ≈ on time
00:47≈ on time ≈ on time
00:55≈ on time ≈ on time
00:58on time on time

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 Nov— 01:140 min+9 min
Tue 3 Nov— 00:180 min—
Sun 1 Nov's-Hertogenbosch 00:140 min—
Sat 31 OctAmsterdam Bijlmer ArenA 23:160 min—
Fri 30 Oct— 00:380 min—
Thu 29 Oct— 00:360 min—
Wed 28 Oct— 22:290 min—
Tue 27 Oct— 01:000 min—
Mon 26 Oct— 01:150 min—
Sun 25 OctBlerick 01:090 min—
Sat 24 OctDordrecht 01:02No data—
Fri 23 Oct— 01:04+3 min+4 min
Thu 22 Oct— 02:100 min—
Wed 21 Oct— 00:590 min—
Tue 20 Oct— 01:100 min—
Mon 19 Oct— 00:160 min—
Sun 18 OctBlerick 01:090 min—
Sat 17 OctBlerick 01:05No data—
Fri 16 Oct— 00:15+1 min+1 min
Thu 15 Oct— 01:110 min—
Wed 14 Oct— 00:590 min—
Tue 13 Oct— 01:000 min—
Mon 12 Oct— 00:590 min—
Sun 11 OctBlerick 01:090 min—
Sat 10 OctRotterdam Blaak 22:030 min—
Fri 9 Oct— 22:290 min+2 min
Thu 8 Oct— 00:590 min—
Wed 7 Oct— 00:590 min—
Tue 6 Oct— 00:590 min—
Mon 5 Oct's-Hertogenbosch 01:32Partial coverage0 min+14 min