Train Arriva 32250 Venlo – Nijmegen

Venlo 14:59 → Nijmegen 15:52 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 16:03 +1 min

  1. Venlo14:59
  2. Blerick15:01
  3. Vierlingsbeek15:20
  4. Boxmeer15:26
  5. Cuijk15:37
  6. Nijmegen Heyendaal15:48
  7. Nijmegen15:52

Next service: tomorrow 14:59 from Venlo · Fri 20 Nov

Next departure 14:59 tomorrow · Venlo
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 17 full · 2 partial · 11 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 27 full · 2 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Nijmegen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 16 Nov Max en route +15 min · last fix heading to Nijmegen Heyendaal +15 min
  • Wed 4 Nov Max en route +14 min · last fix heading to Nijmegen Heyendaal +14 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Nijmegen Heyendaal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
14:59on time on time
15:01≈ on time ≈ on time
15:14 / 15:15≈ on time ≈ +1 min
15:20 / 15:21≈ on time ≈ +2 min
15:26 / 15:30≈ on time ≈ +2 min
15:37 / 15:38≈ on time ≈ +2 min
15:42≈ on time ≈ +3 min
15:48≈ on time ≈ +3 min
15:52on 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
Thu 19 NovNijmegen Heyendaal 16:03Partial coverage+1 min—
Wed 18 NovNijmegen Heyendaal 16:04Partial coverage+1 min+1 min
Tue 17 NovNijmegen Heyendaal 16:03+1 min—
Mon 16 NovNijmegen Heyendaal 16:18+15 min+15 min
Sun 15 NovNijmegen Heyendaal 16:240 min+6 min
Sat 14 NovNijmegen Heyendaal 16:020 min—
Fri 13 NovNijmegen Heyendaal 16:03+1 min—
Thu 12 NovNijmegen Heyendaal 16:020 min—
Wed 11 NovNijmegen Heyendaal 16:07+4 min+4 min
Tue 10 NovNijmegen Heyendaal 16:020 min—
Mon 9 NovNijmegen Heyendaal 16:020 min—
Sun 8 NovNijmegen Heyendaal 16:020 min—
Sat 7 NovNijmegen Heyendaal 16:020 min—
Fri 6 NovNijmegen Heyendaal 16:02No data—
Thu 5 NovNijmegen Heyendaal 16:02No data—
Wed 4 NovNijmegen Heyendaal 16:14+14 min+14 min
Tue 3 NovNijmegen Heyendaal 16:03No data—
Mon 2 NovNijmegen Heyendaal 16:02No data—
Sun 1 NovTegelen 15:09+2 min+3 min
Sat 31 OctTegelen 15:07+1 min+2 min
Fri 30 OctNijmegen Heyendaal 16:03No data—
Thu 29 OctNijmegen Heyendaal 16:020 min—
Wed 28 OctNijmegen Heyendaal 16:050 min—
Tue 27 OctNijmegen Heyendaal 16:06No data—
Mon 26 OctNijmegen Heyendaal 16:02No data—
Sun 25 OctTegelen 15:06No data—
Sat 24 OctTegelen 15:07+1 min+1 min
Fri 23 OctTegelen 15:06No data—
Thu 22 OctTegelen 15:06No data—
Wed 21 OctTegelen 15:09No data—