Train NS 3579 Dordrecht – Venlo

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 20:09 from Dordrecht · Fri 20 Nov

Next departure 20:09 today · Dordrecht
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 23 full · 0 partial · 3 no data
On-time · 90 days
86%
31/36 runs under 3 min
RT coverage: 36 full · 0 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 13 Nov Max en route +10 min · last fix heading to — +9 min
  • Fri 6 Nov Max en route +4 min · last fix heading to — +4 min
  • Wed 7 Oct Max en route +5 min · last fix heading to — +4 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +4 min
  • Sat 14 Nov Max en route +4 min · last fix heading to Helmond +3 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 86% · 31
  • 3–10 min 14% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 83% W n=6
  • 83% T n=6
  • 60% F n=5
  • 75% S n=4
  • 100% 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
20:09on time on time
20:20≈ on time ≈ on time
20:23 / 20:26≈ on time ≈ on time
20:31≈ on time ≈ on time
20:38≈ on time ≈ +1 min
20:45 / 20:47≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:59 / 21:00≈ on time ≈ +1 min
21:15 / 21:16≈ on time ≈ +1 min
21:23 / 21:26≈ on time ≈ +1 min
21:31 / 21:32≈ on time ≈ +1 min
21:48 / 21:54≈ on time ≈ +2 min
22:21 / 22:24≈ on time ≈ +2 min
22:44 / 22:49≈ on time ≈ +3 min
22:58 / 22:59≈ on time ≈ +3 min
23:06≈ on time ≈ +3 min
23:17≈ on time ≈ +3 min
23:25≈ on time ≈ +3 min
23:28on time +4 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 19 Nov— 22:440 min—
Wed 18 Nov— 22:43+3 min+4 min
Tue 17 Nov— 20:340 min—
Sun 15 NovBlerick 23:390 min—
Sat 14 NovHelmond 23:34+3 min+4 min
Fri 13 Nov— 23:24+9 min+10 min
Thu 12 Nov— 23:34+4 min+5 min
Wed 11 Nov— 23:290 min—
Tue 10 Nov— 23:290 min—
Mon 9 Nov— 23:34+3 min+6 min
Sun 8 NovBlerick 23:390 min+1 min
Sat 7 NovHorst-Sevenum 23:240 min—
Fri 6 Nov— 23:34+4 min+4 min
Thu 5 Nov— 23:290 min—
Wed 4 Nov— 22:440 min—
Mon 2 Nov— 23:290 min—
Sun 1 Nov's-Hertogenbosch 22:380 min—
Sat 31 Oct's-Hertogenbosch 22:380 min—
Thu 29 Oct— 22:490 min—
Wed 28 Oct— 20:590 min—
Tue 27 Oct— 23:300 min—
Mon 26 Oct— 23:290 min—
Sun 25 OctBlerick 23:39No data—
Sat 24 Oct's-Hertogenbosch 23:30No data—
Fri 23 Oct— 23:31+1 min—
Thu 22 Oct— 23:29No data—
Wed 21 Oct— 23:36No data—
Mon 19 Oct— 23:290 min—
Sun 18 OctBlerick 23:400 min—
Sat 17 OctBlerick 23:39No data—