Train NS 3581 Dordrecht – Venlo

Dordrecht 20:39 → Venlo 23:58 Daily 3 h 19 min · 19 stops NS (Nederlandse Spoorwegen)

Running now · updated 22:29

Heading to Venlo 0 min

Estimated arrival at Venlo 23:58 · 109 km/h

  1. Dordrecht20:39
  2. Schiedam Centrum21:01
  3. Den Haag Laan v NOI21:20
  4. Amsterdam Zuid21:53
  5. 's-Hertogenbosch22:51
  6. Deurne23:36
  7. Venlo23:58

Today it is running no worse than usual: typical arrival delay is 0 min; 86% of the last 22 runs arrived on time.

On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 19 full · 3 partial · 6 no data
On-time · 90 days
79%
26/33 runs under 3 min
RT coverage: 29 full · 4 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
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

  • Thu 8 Oct Max en route +11 min · last fix heading to — +9 min
  • Fri 13 Nov Max en route +8 min · last fix heading to — +8 min
  • Tue 10 Nov Max en route +6 min · last fix heading to — +6 min
  • Tue 6 Oct Max en route +6 min · last fix heading to — +6 min
  • Mon 9 Nov Max en route +6 min · last fix heading to — +4 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 79% · 26
  • 3–10 min 21% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 60% T n=5
  • 100% W n=5
  • 50% T n=2
  • 60% F n=5
  • 100% S n=5
  • 80% S n=5

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 10Today
20:39on time on time
20:50≈ on time ≈ on time
20:53 / 20:56≈ on time ≈ on time
21:01≈ on time ≈ +1 min
21:08≈ on time ≈ +1 min
21:15 / 21:17≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:29 / 21:30≈ on time ≈ +2 min
21:45 / 21:46≈ on time ≈ +2 min
21:53 / 21:56≈ on time ≈ +2 min
22:02≈ on time ≈ +3 min
22:18 / 22:24≈ on time ≈ +3 min
22:51 / 22:54≈ on time ≈ +4 min
23:14 / 23:19≈ on time ≈ +5 min
23:28 / 23:29≈ on time ≈ +5 min
23:36≈ on time ≈ +5 min
23:47≈ on time ≈ +6 min
23:55≈ on time ≈ +6 min
23:58on time +6 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 16 NovLeiden Centraal 22:24Partial coverage0 min—
Sun 15 NovBlerick 00:09Partial coverage0 min—
Sat 14 Nov's-Hertogenbosch 23:59Partial coverage+1 min+1 min
Fri 13 Nov— 00:15+8 min+8 min
Wed 11 Nov— 00:000 min+2 min
Tue 10 Nov— 00:09+6 min+6 min
Mon 9 Nov— 00:08+4 min+6 min
Sun 8 NovBlerick 00:090 min—
Sat 7 NovEindhoven Centraal 23:330 min—
Fri 6 Nov— 00:040 min+4 min
Thu 5 Nov— 23:14No data—
Wed 4 Nov— 00:02+1 min+2 min
Tue 3 Nov— 23:150 min—
Sun 1 Nov's-Hertogenbosch 23:090 min—
Sat 31 Oct's-Hertogenbosch 23:230 min—
Fri 30 Oct— 23:35No data—
Thu 29 Oct— 23:370 min—
Wed 28 Oct— 21:290 min—
Tue 27 Oct— 00:000 min—
Mon 26 Oct— 00:040 min—
Sun 25 OctBlerick 00:09No data—
Sat 24 OctLeiden Centraal 00:00No data—
Fri 23 Oct— 00:000 min—
Thu 22 Oct— 00:02No data—
Wed 21 Oct— 23:59No data—
Tue 20 Oct— 23:160 min—
Mon 19 Oct— 00:020 min—
Sun 18 OctBlerick 00:120 min—
Sat 17 OctBlerick 00:100 min—
Fri 16 Oct— 00:000 min—