Train NS 3529 Rotterdam Centraal – Venlo

Rotterdam Centraal 07:56 → Venlo 10:58 Daily 3 h 02 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Blerick at 11:09 +1 min

  1. Rotterdam Centraal07:56
  2. Den Haag HS08:15
  3. Leiden Centraal08:29
  4. Amsterdam Bijlmer ArenA09:01
  5. Eindhoven Centraal10:14
  6. Blerick10:55
  7. Venlo10:58

Next service: tomorrow 07:56 from Rotterdam Centraal · Sun 15 Nov

Next departure 07:56 tomorrow · Rotterdam Centraal
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 28 full · 2 partial · 59 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: +1 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

  • Sun 18 Oct Max en route +8 min · last fix heading to Blerick +7 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Blerick +3 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Blerick +3 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 90% · 27
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (17 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 10
07:56on time on time
08:01≈ on time ≈ on time
08:08≈ on time ≈ on time
08:15 / 08:17≈ on time ≈ on time
08:20≈ on time ≈ on time
08:29 / 08:30≈ on time ≈ +1 min
08:45 / 08:46≈ on time ≈ +1 min
08:53 / 08:56≈ on time ≈ +1 min
09:01 / 09:02≈ on time ≈ +1 min
09:18 / 09:24≈ on time ≈ +1 min
09:51 / 09:54≈ on time ≈ +2 min
10:14 / 10:19≈ on time ≈ +2 min
10:28 / 10:29≈ on time ≈ +3 min
10:36≈ on time ≈ +3 min
10:47≈ on time ≈ +3 min
10:55≈ on time ≈ +3 min
10:58on 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 14 NovBlerick 11:09Partial coverage+1 min+1 min
Fri 13 NovBlerick 11:090 min—
Thu 12 NovBlerick 11:090 min—
Wed 11 NovBlerick 11:130 min—
Tue 10 NovBlerick 11:12+3 min+4 min
Mon 9 NovBlerick 11:090 min+1 min
Sun 8 NovBlerick 11:090 min—
Sat 7 NovBlerick 11:090 min—
Fri 6 NovBlerick 11:29No data—
Thu 5 NovBlerick 11:09No data—
Wed 4 NovBlerick 11:090 min—
Tue 3 NovBlerick 11:09No data—
Mon 2 NovBlerick 11:14No data—
Sun 1 Nov's-Hertogenbosch 10:150 min—
Sat 31 Oct's-Hertogenbosch 10:150 min—
Fri 30 OctHelmond 't Hout 10:440 min—
Thu 29 OctBlerick 11:090 min—
Wed 28 OctBlerick 11:090 min—
Tue 27 OctBlerick 11:090 min—
Mon 26 OctBlerick 11:090 min—
Sun 25 OctBlerick 11:09No data—
Sat 24 OctBlerick 11:090 min—
Fri 23 OctBlerick 11:090 min—
Thu 22 OctBlerick 11:09No data—
Wed 21 OctBlerick 11:09No data—
Tue 20 OctBlerick 11:090 min—
Mon 19 OctBlerick 11:130 min—
Sun 18 OctBlerick 11:17+7 min+8 min
Sat 17 OctBlerick 11:090 min—
Fri 16 OctBlerick 11:090 min—