Train NS 3582 Venlo – Utrecht Centraal

Venlo 21:33 → Utrecht Centraal 23:06 Daily 1 h 33 min · 8 stops NS (Nederlandse Spoorwegen)

Running now · updated 00:29

Heading to Utrecht Centraal No data

Estimated arrival at Utrecht Centraal 23:06 · 8 km/h

  1. Venlo21:33
  2. Blerick21:36
  3. Horst-Sevenum21:43
  4. Helmond22:01
  5. Eindhoven Centraal22:11
  6. 's-Hertogenbosch22:36
  7. Utrecht Centraal23:06
On-time · 30 days
81%
21/26 runs under 3 min
RT coverage: 26 full · 0 partial · 1 no data
On-time · 90 days
83%
25/30 runs under 3 min
RT coverage: 30 full · 0 partial · 17 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: +7 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

  • Sat 10 Oct Max en route +9 min · last fix heading to Helmond +8 min
  • Wed 4 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 23 Oct Max en route +7 min · last fix heading to — +7 min
  • Wed 14 Oct Max en route +7 min · last fix heading to — +6 min
  • Sun 18 Oct Max en route +6 min · last fix heading to 's-Hertogenbosch +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 25
  • 3–10 min 17% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 60% W n=5
  • 100% T n=5
  • 75% F n=4
  • 75% S n=4
  • 67% S n=3

Stops and timetable

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

Last 90 days, 30 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
21:33on time on time
21:36≈ on time ≈ on time
21:43≈ on time ≈ +1 min
21:54≈ on time ≈ +1 min
22:01≈ on time ≈ +2 min
22:11 / 22:16≈ on time ≈ +3 min
22:36 / 22:40≈ on time ≈ +4 min
23:06on 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 6 Nov— 00:24+1 min+5 min
Thu 5 Nov— 00:330 min—
Wed 4 Nov— 23:22+8 min+8 min
Tue 3 Nov— 00:290 min—
Sun 1 Nov's-Hertogenbosch 23:070 min—
Sat 31 Oct's-Hertogenbosch 23:230 min—
Thu 29 Oct— 00:350 min—
Wed 28 Oct— 23:130 min—
Tue 27 Oct— 00:340 min—
Mon 26 Oct— 23:230 min—
Sun 25 Oct's-Hertogenbosch 23:53No data—
Sat 24 Oct's-Hertogenbosch 00:330 min—
Fri 23 Oct— 22:25+7 min+7 min
Thu 22 Oct— 23:080 min—
Wed 21 Oct— 23:200 min—
Tue 20 Oct— 23:020 min—
Mon 19 Oct— 23:230 min—
Sun 18 Oct's-Hertogenbosch 23:23+6 min+6 min
Sat 17 Oct's-Hertogenbosch 23:140 min—
Fri 16 Oct— 00:32+1 min+4 min
Thu 15 Oct— 00:320 min—
Wed 14 Oct— 23:20+6 min+7 min
Tue 13 Oct— 00:330 min—
Mon 12 Oct— 00:320 min—
Sun 11 Oct's-Hertogenbosch 23:070 min—
Sat 10 OctHelmond 23:54+8 min+9 min
Fri 9 Oct— 23:230 min—
Thu 8 Oct— 23:240 min—
Wed 7 Oct— 23:070 min—
Tue 6 Oct— 00:300 min—