Train NS 3527 Dordrecht – Venlo

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

✓ Today’s run finished

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

  1. Dordrecht07:04
  2. Schiedam Centrum07:27
  3. Den Haag Laan v NOI07:46
  4. Amsterdam Zuid08:22
  5. 's-Hertogenbosch09:22
  6. Blerick10:25
  7. Venlo10:28

Next service: tomorrow 07:04 from Dordrecht · Fri 6 Nov

Next departure 07:04 tomorrow · Dordrecht
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 19 full · 9 partial · 2 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 19 full · 10 partial · 60 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

  • Wed 4 Nov Max en route +27 min · last fix heading to Blerick +20 min
  • Fri 9 Oct 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 93% · 27
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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
07:04on time on time
07:15≈ on time ≈ on time
07:18 / 07:22≈ on time ≈ on time
07:27≈ on time ≈ on time
07:34≈ on time ≈ on time
07:41 / 07:43≈ on time ≈ on time
07:46≈ on time ≈ on time
07:55 / 07:57≈ on time ≈ +1 min
08:14 / 08:15≈ on time ≈ +1 min
08:22 / 08:26≈ on time ≈ +1 min
08:31 / 08:32≈ on time ≈ +1 min
08:48 / 08:54≈ on time ≈ +1 min
09:22 / 09:25≈ on time ≈ +1 min
09:45 / 09:49≈ on time ≈ +2 min
09:58 / 09:59≈ on time ≈ +2 min
10:06≈ on time ≈ +2 min
10:17≈ on time ≈ +2 min
10:25≈ on time ≈ +2 min
10:28on time +2 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 10:39Partial coverage0 min—
Wed 4 NovBlerick 10:39+20 min+27 min
Tue 3 NovBlerick 10:40Partial coverage0 min—
Mon 2 NovBlerick 10:39Partial coverage0 min—
Sun 1 Nov's-Hertogenbosch 09:390 min—
Sat 31 Oct's-Hertogenbosch 09:390 min—
Fri 30 OctHelmond 't Hout 10:140 min—
Thu 29 OctBlerick 10:39Partial coverage0 min—
Wed 28 OctBlerick 10:400 min—
Tue 27 OctBlerick 10:390 min—
Mon 26 OctBlerick 10:390 min—
Sun 25 OctBlerick 10:39No data—
Sat 24 OctBlerick 10:41+2 min+2 min
Fri 23 OctBlerick 10:410 min—
Thu 22 OctBlerick 10:410 min—
Wed 21 OctBlerick 10:400 min—
Tue 20 OctBlerick 10:390 min—
Mon 19 OctBlerick 10:41Partial coverage0 min—
Sun 18 OctBlerick 10:46No data—
Sat 17 OctBlerick 10:390 min—
Fri 16 OctBlerick 10:390 min—
Thu 15 Oct's-Hertogenbosch 10:58Partial coverage0 min—
Wed 14 OctBlerick 10:400 min—
Tue 13 OctBlerick 10:40Partial coverage0 min—
Mon 12 OctBlerick 10:39Partial coverage0 min—
Sun 11 OctBlerick 10:390 min+2 min
Sat 10 OctBlerick 10:390 min—
Fri 9 OctBlerick 10:43+4 min+4 min
Thu 8 OctBlerick 10:40Partial coverage+1 min+1 min
Wed 7 OctHorst-Sevenum 12:000 min—