Train NS 3525 Dordrecht – Venlo

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

✓ Today’s run finished

Today, last fix heading to Blerick at 10:09 0 min

  1. Dordrecht06:34
  2. Schiedam Centrum06:57
  3. Den Haag Laan v NOI07:16
  4. Amsterdam Zuid07:52
  5. 's-Hertogenbosch08:52
  6. Blerick09:55
  7. Venlo09:58

Next service: tomorrow 06:34 from Dordrecht · Tue 10 Nov

Next departure 06:34 tomorrow · Dordrecht
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 22 full · 6 partial · 2 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 26 full · 7 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Sun 18 Oct Max en route +8 min · last fix heading to Blerick +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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