Train NS 3548 Venlo – Delft Campus

Venlo 13:03 → Delft Campus 15:55 Daily 2 h 52 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 13:03 from Venlo · Sun 8 Nov

Next departure 13:03 today · Venlo
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 17 full · 1 partial · 11 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 31 Oct Max en route +8 min · last fix heading to Rotterdam Stadion +8 min
  • Sat 10 Oct Max en route +8 min · last fix heading to Rotterdam Blaak +8 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Rotterdam Blaak +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
13:03on time on time
13:06≈ on time ≈ on time
13:13≈ on time ≈ on time
13:24≈ on time ≈ on time
13:31≈ on time ≈ +1 min
13:41 / 13:46≈ on time ≈ +1 min
14:06 / 14:10≈ on time ≈ +1 min
14:36 / 14:41≈ on time ≈ +2 min
14:58≈ on time ≈ +2 min
15:04 / 15:07≈ on time ≈ +2 min
15:13 / 15:14≈ on time ≈ +2 min
15:30 / 15:32≈ on time ≈ +3 min
15:40 / 15:41≈ on time ≈ +3 min
15:44 / 15:45≈ on time ≈ +3 min
15:52≈ on time ≈ +3 min
15:55on time +3 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 16:04Partial coverage0 min—
Fri 6 NovRotterdam Blaak 16:28No data—
Thu 5 NovRotterdam Blaak 16:32No data—
Wed 4 NovRotterdam Blaak 16:290 min—
Tue 3 NovRotterdam Blaak 16:29No data—
Mon 2 NovRotterdam Blaak 16:29No data—
Sun 1 NovRotterdam Blaak 16:260 min—
Sat 31 OctRotterdam Stadion 16:45+8 min+8 min
Fri 30 OctRotterdam Blaak 16:240 min—
Thu 29 OctRotterdam Blaak 16:360 min—
Wed 28 OctRotterdam Blaak 16:310 min—
Tue 27 OctRotterdam Blaak 16:310 min—
Mon 26 OctRotterdam Blaak 16:310 min—
Sun 25 OctRotterdam Blaak 16:25No data—
Sat 24 OctRotterdam Blaak 16:250 min+3 min
Fri 23 OctRotterdam Blaak 16:27No data—
Thu 22 OctRotterdam Blaak 16:300 min—
Wed 21 OctRotterdam Blaak 16:30No data—
Tue 20 OctRotterdam Blaak 16:320 min—
Mon 19 OctRotterdam Blaak 16:300 min—
Sun 18 OctRotterdam Blaak 16:27+2 min+3 min
Sat 17 OctRotterdam Blaak 16:250 min—
Fri 16 OctRotterdam Blaak 16:27No data—
Thu 15 OctRotterdam Blaak 16:31No data—
Wed 14 OctRotterdam Blaak 16:30No data—
Tue 13 OctRotterdam Blaak 16:30No data—
Mon 12 OctRotterdam Blaak 16:300 min—
Sun 11 OctRotterdam Blaak 16:260 min—
Sat 10 OctRotterdam Blaak 16:24+8 min+8 min
Fri 9 OctRotterdam Blaak 16:250 min—