Train NS 3584 Venlo – Utrecht Centraal

Venlo 22:03 → Utrecht Centraal 23:36 Daily 1 h 33 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 22:03 from Venlo · Wed 18 Nov

Next departure 22:03 today · Venlo
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 23 full · 2 partial · 3 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 35 full · 4 partial · 17 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: +2 min

Last 30 days

Arrival delay at Utrecht Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +7 min · last fix heading to 's-Hertogenbosch +6 min
  • Thu 12 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
22:03on time on time
22:06≈ on time ≈ on time
22:13≈ on time ≈ on time
22:24≈ on time ≈ on time
22:31≈ on time ≈ +1 min
22:41 / 22:46≈ on time ≈ +1 min
23:06 / 23:10≈ on time ≈ +1 min
23:36on 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
Tue 17 Nov— 00:59+1 min+5 min
Mon 16 Nov's-Hertogenbosch 23:44Partial coverage+2 min+4 min
Sun 15 Nov's-Hertogenbosch 23:530 min—
Sat 14 NovEindhoven Centraal 01:090 min+1 min
Fri 13 Nov— 01:330 min+44 min
Thu 12 Nov— 23:39+3 min+3 min
Wed 11 Nov— 01:020 min+1 min
Tue 10 Nov— 01:02+2 min+5 min
Mon 9 Nov— 23:54+2 min+3 min
Sun 8 Nov's-Hertogenbosch 23:54+1 min+2 min
Sat 7 Nov's-Hertogenbosch 23:240 min—
Fri 6 Nov— 01:040 min+16 min
Thu 5 Nov— 23:380 min—
Wed 4 Nov— 00:590 min—
Tue 3 Nov— 23:540 min—
Mon 2 Nov— 00:59+1 min—
Sun 1 Nov's-Hertogenbosch 23:240 min—
Sat 31 Oct's-Hertogenbosch 01:100 min—
Fri 30 Oct— 23:530 min—
Thu 29 Oct— 01:000 min+2 min
Tue 27 Oct— 23:27No data—
Mon 26 Oct— 01:010 min—
Sun 25 Oct's-Hertogenbosch 01:02Partial coverage0 min—
Sat 24 OctHelmond 01:010 min—
Fri 23 Oct— 01:010 min+3 min
Thu 22 Oct— 23:37No data—
Wed 21 Oct— 01:01No data—
Tue 20 Oct— 01:000 min—
Mon 19 Oct— 23:37No data—
Sun 18 Oct's-Hertogenbosch 23:53+6 min+7 min