Train NS 3527 Utrecht Centraal – Venlo

Utrecht Centraal 08:54 → Venlo 10:28 Daily 1 h 34 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 10:39 +1 min

  1. Utrecht Centraal08:54
  2. 's-Hertogenbosch09:21
  3. Eindhoven Centraal09:44
  4. Deurne10:06
  5. Horst-Sevenum10:17
  6. Blerick10:25
  7. Venlo10:28

Next service: tomorrow 08:54 from Utrecht Centraal · Mon 9 Nov

Next departure 08:54 tomorrow · Utrecht Centraal
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 26 full · 1 partial · 3 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 30 full · 1 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 4 Nov Max en route +27 min · last fix heading to Blerick +20 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Blerick +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
08:54on time on time
09:21 / 09:24≈ on time ≈ on time
09:44 / 09:49≈ on time ≈ on time
09:58 / 09:59≈ on time ≈ +1 min
10:06≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:25≈ on time ≈ +1 min
10:28on time +1 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
Sun 8 NovBlerick 10:39Partial coverage+1 min—
Sat 7 NovBlerick 10:390 min—
Fri 6 NovBlerick 10:42No data—
Thu 5 NovBlerick 10:390 min—
Wed 4 NovBlerick 10:39+20 min+27 min
Tue 3 NovBlerick 10:400 min—
Mon 2 NovBlerick 10:390 min—
Sun 1 Nov's-Hertogenbosch 09:390 min—
Sat 31 Oct's-Hertogenbosch 09:390 min—
Fri 30 OctHelmond 't Hout 10:140 min—
Thu 29 OctBlerick 10:390 min—
Wed 28 OctBlerick 10:400 min—
Tue 27 OctBlerick 10:390 min—
Mon 26 OctBlerick 10:390 min—
Sun 25 OctBlerick 10:39No data—
Sat 24 OctBlerick 10:41+2 min+2 min
Fri 23 OctBlerick 10:410 min—
Thu 22 OctBlerick 10:410 min—
Wed 21 OctBlerick 10:400 min—
Tue 20 OctBlerick 10:390 min—
Mon 19 OctBlerick 10:410 min—
Sun 18 OctBlerick 10:46No data—
Sat 17 OctBlerick 10:390 min—
Fri 16 OctBlerick 10:390 min—
Thu 15 Oct's-Hertogenbosch 10:580 min—
Wed 14 OctBlerick 10:400 min—
Tue 13 OctBlerick 10:400 min—
Mon 12 OctBlerick 10:390 min—
Sun 11 OctBlerick 10:390 min+2 min
Sat 10 OctBlerick 10:390 min—