Train NS 3533 Dordrecht – Venlo

Dordrecht 08:34 → Venlo 11:58 Daily 3 h 24 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 12:09 No data

  1. Dordrecht08:34
  2. Schiedam Centrum08:57
  3. Den Haag Laan v NOI09:16
  4. Amsterdam Zuid09:52
  5. 's-Hertogenbosch10:52
  6. Blerick11:55
  7. Venlo11:58

Next service: tomorrow 08:34 from Dordrecht · Fri 6 Nov

Next departure 08:34 tomorrow · Dordrecht
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 14 full · 5 partial · 11 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 14 full · 6 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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 +10 min · last fix heading to Blerick +10 min
  • Fri 9 Oct Max en route +7 min · last fix heading to Blerick +7 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Blerick +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
08:34on time on time
08:45≈ on time ≈ on time
08:48 / 08:52≈ on time ≈ on time
08:57≈ on time ≈ +1 min
09:04≈ on time ≈ +1 min
09:11 / 09:13≈ on time ≈ +1 min
09:16≈ on time ≈ +1 min
09:25 / 09:27≈ on time ≈ +1 min
09:44 / 09:45≈ on time ≈ +2 min
09:52 / 09:56≈ on time ≈ +2 min
10:01 / 10:02≈ on time ≈ +2 min
10:18 / 10:24≈ on time ≈ +3 min
10:52 / 10:55≈ on time ≈ +3 min
11:15 / 11:19≈ on time ≈ +4 min
11:28 / 11:29≈ on time ≈ +4 min
11:36≈ on time ≈ +4 min
11:47≈ on time ≈ +5 min
11:55≈ on time ≈ +5 min
11:58on time +5 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 5 NovBlerick 12:09No data—
Wed 4 NovBlerick 12:12Partial coverage+3 min+3 min
Tue 3 NovBlerick 12:39No data—
Mon 2 NovBlerick 12:19No data—
Sun 1 Nov's-Hertogenbosch 11:17+1 min+1 min
Sat 31 Oct's-Hertogenbosch 11:160 min—
Fri 30 OctHelmond 't Hout 11:440 min—
Thu 29 OctBlerick 12:10Partial coverage0 min—
Wed 28 OctBlerick 12:090 min—
Tue 27 OctBlerick 12:190 min—
Mon 26 OctBlerick 12:09No data—
Sun 25 OctBlerick 12:11No data—
Sat 24 OctBlerick 12:090 min—
Fri 23 OctBlerick 12:090 min—
Thu 22 OctBlerick 12:15No data—
Wed 21 OctBlerick 12:16No data—
Tue 20 OctBlerick 12:090 min—
Mon 19 OctBlerick 12:09Partial coverage0 min—
Sun 18 OctBlerick 12:19+10 min+10 min
Sat 17 OctBlerick 12:100 min—
Fri 16 OctBlerick 12:090 min—
Thu 15 OctBlerick 12:14No data—
Wed 14 OctBlerick 12:13No data—
Tue 13 OctBlerick 12:09No data—
Mon 12 OctBlerick 12:09No data—
Sun 11 OctBlerick 12:090 min—
Sat 10 OctBlerick 12:090 min—
Fri 9 OctBlerick 12:16+7 min+7 min
Thu 8 OctBlerick 12:09Partial coverage+1 min+1 min
Wed 7 OctBlerick 12:09Partial coverage0 min—