Train NS 3539 Dordrecht – Venlo

Dordrecht 10:09 → Venlo 13:28 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +2 min

Next service: today 10:09 from Dordrecht · Mon 16 Nov

Next departure 10:09 today · Dordrecht
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 22 full · 4 partial · 3 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 29 full · 7 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 34
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=6
  • 100% T n=5
  • 100% F n=3
  • 100% S n=6
  • 80% S n=5

Stops and timetable

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

Last 90 days, 36 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
10:09on time on time
10:20≈ on time ≈ on time
10:23 / 10:26≈ on time ≈ on time
10:31≈ on time ≈ on time
10:38≈ on time ≈ on time
10:45 / 10:47≈ on time ≈ on time
10:50≈ on time ≈ on time
10:59 / 11:00≈ on time ≈ on time
11:15 / 11:16≈ on time ≈ on time
11:23 / 11:26≈ on time ≈ on time
11:31 / 11:32≈ on time ≈ on time
11:48 / 11:54≈ on time ≈ on time
12:21 / 12:24≈ on time ≈ +1 min
12:44 / 12:49≈ on time ≈ +1 min
12:58 / 12:59≈ on time ≈ +1 min
13:06≈ on time ≈ +1 min
13:17≈ on time ≈ +1 min
13:25≈ on time ≈ +1 min
13:28on 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
Sun 15 NovBlerick 13:40Partial coverage+2 min+2 min
Sat 14 NovBlerick 13:39Partial coverage+2 min+2 min
Fri 13 NovBlerick 13:39Partial coverage0 min—
Thu 12 NovBlerick 13:39+1 min+1 min
Wed 11 NovBlerick 13:390 min—
Tue 10 NovBlerick 13:390 min—
Mon 9 NovBlerick 13:390 min—
Sun 8 NovBlerick 13:390 min—
Sat 7 NovBlerick 13:390 min—
Fri 6 NovBlerick 13:39No data—
Thu 5 NovBlerick 13:440 min—
Wed 4 NovBlerick 13:390 min—
Tue 3 NovBlerick 13:390 min—
Mon 2 NovBlerick 13:440 min—
Sun 1 Nov's-Hertogenbosch 12:460 min—
Sat 31 Oct's-Hertogenbosch 12:450 min—
Fri 30 OctHelmond 't Hout 13:160 min—
Thu 29 OctBlerick 13:420 min—
Wed 28 OctBlerick 13:390 min—
Tue 27 OctBlerick 13:410 min—
Mon 26 OctBlerick 13:390 min—
Sun 25 OctBlerick 13:40No data—
Sat 24 OctBlerick 13:390 min—
Fri 23 OctBlerick 13:39No data—
Thu 22 OctBlerick 13:390 min—
Wed 21 OctBlerick 13:390 min—
Tue 20 OctBlerick 13:420 min—
Mon 19 OctBlerick 13:420 min—
Sun 18 OctBlerick 13:44Partial coverage+5 min+7 min
Sat 17 OctBlerick 13:390 min—