Train NS 3522 Venlo – Delft Campus

Venlo 06:33 → Delft Campus 09:25 Daily 2 h 52 min · 16 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 06:33 from Venlo · Mon 9 Nov

Next departure 06:33 tomorrow · Venlo
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 2 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 50 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: +1 min

Last 30 days

Arrival delay at Delft Campus, 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 9 Oct Max en route +7 min · last fix heading to Rotterdam Blaak +7 min
  • Sat 24 Oct Max en route +6 min · last fix heading to Rotterdam Blaak +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
06:33on time on time
06:36≈ on time ≈ on time
06:43≈ on time ≈ on time
06:54≈ on time ≈ on time
07:01≈ on time ≈ on time
07:11 / 07:16≈ on time ≈ on time
07:36 / 07:40≈ on time ≈ +1 min
08:06 / 08:11≈ on time ≈ +1 min
08:28≈ on time ≈ +1 min
08:34 / 08:37≈ on time ≈ +1 min
08:43 / 08:44≈ on time ≈ +2 min
09:00 / 09:02≈ on time ≈ +2 min
09:10 / 09:11≈ on time ≈ +2 min
09:14 / 09:15≈ on time ≈ +2 min
09:22≈ on time ≈ +2 min
09:25on 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
Sat 7 NovDelft 09:34Partial coverage0 min—
Fri 6 NovRotterdam Blaak 10:14No data—
Thu 5 NovRotterdam Blaak 09:590 min—
Wed 4 NovRotterdam Blaak 09:590 min—
Tue 3 NovRotterdam Blaak 09:590 min—
Mon 2 NovRotterdam Blaak 09:59No data—
Sun 1 Nov's-Hertogenbosch 07:56+2 min+2 min
Sat 31 OctRotterdam Blaak 09:550 min—
Fri 30 OctRotterdam Blaak 09:540 min—
Thu 29 OctRotterdam Blaak 09:590 min—
Wed 28 OctRotterdam Blaak 09:59+3 min+4 min
Tue 27 OctRotterdam Blaak 09:590 min—
Mon 26 OctRotterdam Blaak 10:010 min—
Sat 24 OctRotterdam Blaak 10:04+4 min+6 min
Fri 23 OctRotterdam Blaak 09:560 min—
Thu 22 OctRotterdam Blaak 09:590 min—
Wed 21 OctRotterdam Blaak 09:590 min—
Tue 20 OctRotterdam Centraal 10:140 min—
Mon 19 OctRotterdam Blaak 09:590 min—
Sat 17 OctRotterdam Blaak 09:55+1 min+1 min
Fri 16 OctRotterdam Blaak 09:540 min—
Thu 15 OctSchiedam Centrum 10:580 min—
Wed 14 OctRotterdam Blaak 10:000 min—
Tue 13 OctRotterdam Blaak 10:000 min—
Mon 12 OctRotterdam Blaak 10:000 min—
Sat 10 OctRotterdam Blaak 09:560 min—
Fri 9 OctRotterdam Blaak 10:07+7 min+7 min
Thu 8 OctRotterdam Blaak 09:590 min—
Wed 7 OctRotterdam Blaak 09:590 min—
Tue 6 OctRotterdam Blaak 09:590 min—