Train NS 3581 Dordrecht → Venlo

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 20:37 from Dordrecht · Sat 21 Nov

Next departure 20:37 today · Dordrecht
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 23 full · 0 partial · 4 no data
On-time · 90 days
78%
29/37 runs under 3 min
RT coverage: 37 full · 0 partial · 20 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: +6 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 17 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 29
  • 3–10 min 22% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 50% T n=6
  • 100% W n=6
  • 67% T n=3
  • 67% F n=6
  • 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, 37 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
20:37on time on time
20:50≈ on time ≈ on time
20:53 / 20:56≈ on time ≈ +1 min
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
Fri 20 Nov— 00:040 min+2 min
Thu 19 Nov— 23:59+1 min—
Wed 18 Nov— 20:540 min—
Tue 17 Nov— 23:28+8 min+8 min
Mon 16 NovHelmond 23:590 min+2 min
Sun 15 NovBlerick 00:090 min—
Sat 14 Nov's-Hertogenbosch 23:59+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—