Train Arriva 32228 Venlo – Nijmegen

Venlo 09:29 → Nijmegen 10:22 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 10:32 0 min

  1. Venlo09:29
  2. Blerick09:31
  3. Vierlingsbeek09:50
  4. Boxmeer09:56
  5. Cuijk10:07
  6. Nijmegen Heyendaal10:18
  7. Nijmegen10:22

Next service: tomorrow 09:29 from Venlo · Fri 20 Nov

Next departure 09:29 tomorrow · Venlo
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 9 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 28 full · 2 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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 +8 min · last fix heading to Tegelen +8 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 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=5
  • 100% T n=4
  • 100% F n=2
  • 100% S n=5
  • 80% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
09:29on time on time
09:31≈ on time ≈ on time
09:44 / 09:45≈ on time ≈ +1 min
09:50 / 09:51≈ on time ≈ +1 min
09:56 / 10:00≈ on time ≈ +1 min
10:07 / 10:08≈ on time ≈ +1 min
10:12≈ on time ≈ +1 min
10:18≈ on time ≈ +1 min
10:22on 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 10:32Partial coverage0 min—
Wed 18 NovNijmegen Heyendaal 10:34Partial coverage+1 min—
Tue 17 NovNijmegen Heyendaal 10:34+2 min+2 min
Mon 16 NovNijmegen Heyendaal 10:34+1 min—
Sun 15 NovNijmegen Heyendaal 10:34+1 min—
Sat 14 NovNijmegen Heyendaal 10:33+1 min—
Fri 13 NovNijmegen Heyendaal 10:330 min—
Thu 12 NovNijmegen Heyendaal 10:33+1 min—
Wed 11 NovNijmegen Heyendaal 10:320 min—
Tue 10 NovNijmegen Heyendaal 10:33+1 min—
Mon 9 NovNijmegen Heyendaal 10:34+1 min—
Sun 8 NovNijmegen Heyendaal 10:320 min—
Sat 7 NovNijmegen Heyendaal 10:320 min—
Fri 6 NovNijmegen Heyendaal 10:33No data—
Thu 5 NovNijmegen Heyendaal 10:32No data—
Wed 4 NovNijmegen Heyendaal 10:33+1 min—
Tue 3 NovNijmegen Heyendaal 10:320 min—
Mon 2 NovNijmegen Heyendaal 10:340 min—
Sun 1 NovTegelen 09:37+1 min—
Sat 31 OctTegelen 09:37+2 min+2 min
Fri 30 OctNijmegen Heyendaal 10:32No data—
Thu 29 OctNijmegen Heyendaal 10:330 min—
Wed 28 OctNijmegen Heyendaal 10:320 min—
Tue 27 OctNijmegen Heyendaal 10:330 min—
Mon 26 OctNijmegen Heyendaal 10:33No data—
Sun 25 OctTegelen 09:37No data—
Sat 24 OctTegelen 09:36No data—
Fri 23 OctTegelen 09:35No data—
Thu 22 OctTegelen 09:36No data—
Wed 21 OctTegelen 09:35No data—