Train NS 3537 Rotterdam Centraal – Venlo

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

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 09:56 from Rotterdam Centraal · Mon 16 Nov

Next departure 09:56 today · Rotterdam Centraal
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 21 full · 1 partial · 7 no data
On-time · 90 days
81%
25/31 runs under 3 min
RT coverage: 30 full · 1 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Thu 8 Oct Max en route +40 min · last fix heading to Blerick +40 min
  • Wed 11 Nov Max en route +8 min · last fix heading to Blerick +8 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Blerick +8 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Blerick +5 min
  • Wed 4 Nov 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 81% · 25
  • 3–10 min 16% · 5
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

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

Stops and timetable

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