Train Arriva 32230 Venlo – Nijmegen

Venlo 09:59 → Nijmegen 10:52 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 09:59 from Venlo · Fri 20 Nov

Next departure 09:59 today · Venlo
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 13 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 18 Oct Max en route +7 min · last fix heading to Tegelen +7 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 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • 75% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
09:59on time on time
10:01≈ on time ≈ on time
10:14 / 10:15≈ on time ≈ on time
10:20 / 10:21≈ on time ≈ on time
10:26 / 10:30≈ on time ≈ on time
10:37 / 10:38≈ on time ≈ +1 min
10:42≈ on time ≈ +1 min
10:48≈ on time ≈ +1 min
10:52on time +1 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 11:04Partial coverage+1 min+1 min
Wed 18 NovNijmegen Heyendaal 11:00Partial coverage0 min—
Tue 17 NovNijmegen Heyendaal 11:03+1 min—
Mon 16 NovNijmegen Heyendaal 11:020 min—
Sun 15 NovNijmegen Heyendaal 11:04+1 min—
Sat 14 NovNijmegen Heyendaal 11:020 min—
Fri 13 NovNijmegen Heyendaal 11:030 min—
Thu 12 NovNijmegen Heyendaal 11:020 min—
Wed 11 NovNijmegen Heyendaal 11:020 min—
Tue 10 NovNijmegen Heyendaal 11:020 min—
Mon 9 NovNijmegen Heyendaal 11:020 min—
Sun 8 NovNijmegen Heyendaal 11:03+1 min—
Sat 7 NovNijmegen Heyendaal 11:020 min—
Fri 6 NovNijmegen Heyendaal 11:02No data—
Thu 5 NovNijmegen Heyendaal 11:02No data—
Wed 4 NovNijmegen Heyendaal 11:03+1 min—
Tue 3 NovNijmegen Heyendaal 11:03No data—
Mon 2 NovNijmegen Heyendaal 11:02No data—
Sun 1 NovTegelen 10:06No data—
Sat 31 OctTegelen 10:060 min—
Fri 30 OctNijmegen Heyendaal 11:02No data—
Thu 29 OctNijmegen Heyendaal 11:02No data—
Wed 28 OctNijmegen Heyendaal 11:020 min—
Tue 27 OctNijmegen Heyendaal 11:17No data—
Mon 26 OctNijmegen Heyendaal 11:02No data—
Sun 25 OctTegelen 10:06No data—
Sat 24 OctTegelen 10:06No data—
Fri 23 OctTegelen 10:06No data—
Thu 22 OctTegelen 10:09No data—
Wed 21 OctTegelen 10:06No data—