Train NS 3535 Dordrecht – Venlo

Dordrecht 09:09 → Venlo 12: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 09:09 from Dordrecht · Sun 15 Nov

Next departure 09:09 today · Dordrecht
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 19 full · 2 partial · 8 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 25 full · 4 partial · 59 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: +4 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

  • Sun 18 Oct Max en route +31 min · last fix heading to Helmond +31 min
  • Sun 1 Nov Max en route +10 min · last fix heading to 's-Hertogenbosch +10 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Blerick +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 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=6
  • 50% 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
09:09on time on time
09:20≈ on time ≈ on time
09:23 / 09:26≈ on time ≈ on time
09:31≈ on time ≈ on time
09:38≈ on time ≈ +1 min
09:45 / 09:47≈ on time ≈ +1 min
09:50≈ on time ≈ +1 min
09:59 / 10:00≈ on time ≈ +1 min
10:15 / 10:16≈ on time ≈ +1 min
10:23 / 10:26≈ on time ≈ +1 min
10:31 / 10:32≈ on time ≈ +2 min
10:48 / 10:54≈ on time ≈ +2 min
11:21 / 11:24≈ on time ≈ +3 min
11:44 / 11:49≈ on time ≈ +3 min
11:58 / 11:59≈ on time ≈ +3 min
12:06≈ on time ≈ +3 min
12:17≈ on time ≈ +4 min
12:25≈ on time ≈ +4 min
12: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
Sat 14 NovBlerick 12:39Partial coverage0 min—
Fri 13 NovBlerick 12:39Partial coverage+2 min+2 min
Thu 12 NovBlerick 12:390 min—
Wed 11 NovBlerick 12:39+1 min—
Tue 10 NovBlerick 12:39+4 min+4 min
Mon 9 NovBlerick 12:390 min—
Sun 8 NovBlerick 12:39+1 min—
Sat 7 NovBlerick 12:390 min—
Fri 6 NovBlerick 12:42No data—
Thu 5 NovBlerick 12:39No data—
Wed 4 NovBlerick 12:39+1 min+1 min
Tue 3 NovBlerick 12:54No data—
Mon 2 NovBlerick 12:44No data—
Sun 1 Nov's-Hertogenbosch 12:04+10 min+10 min
Sat 31 Oct's-Hertogenbosch 11:450 min—
Fri 30 OctHelmond 't Hout 12:160 min—
Thu 29 OctBlerick 12:400 min—
Wed 28 OctBlerick 12:390 min—
Tue 27 OctBlerick 12:390 min—
Mon 26 OctBlerick 12:39No data—
Sun 25 OctBlerick 12:45No data—
Sat 24 OctBlerick 12:39+1 min—
Fri 23 OctBlerick 12:41No data—
Thu 22 OctBlerick 12:420 min—
Wed 21 OctBlerick 12:39No data—
Tue 20 OctBlerick 12:390 min—
Mon 19 OctBlerick 12:390 min—
Sun 18 OctHelmond 13:29+31 min+31 min
Sat 17 OctBlerick 12:390 min—
Fri 16 OctBlerick 12:39No data—