Train Arriva 32218 Venlo – Nijmegen

Venlo 06:59 → Nijmegen 07:52 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 08:03 0 min

  1. Venlo06:59
  2. Blerick07:01
  3. Vierlingsbeek07:20
  4. Boxmeer07:26
  5. Cuijk07:37
  6. Nijmegen Heyendaal07:48
  7. Nijmegen07:52

Next service: tomorrow 06:59 from Venlo · Sun 15 Nov

Next departure 06:59 tomorrow · Venlo
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 18 full · 3 partial · 3 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 25 full · 5 partial · 52 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: +3 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

  • Wed 11 Nov Max en route +17 min · last fix heading to Nijmegen Heyendaal +16 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Nijmegen Heyendaal +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 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 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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
06:59on time on time
07:01≈ on time ≈ on time
07:14 / 07:15≈ on time ≈ +1 min
07:20 / 07:21≈ on time ≈ +2 min
07:26 / 07:30≈ on time ≈ +2 min
07:37 / 07:38≈ on time ≈ +3 min
07:42≈ on time ≈ +3 min
07:48≈ on time ≈ +3 min
07:52on time +4 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 NovNijmegen Heyendaal 08:03Partial coverage0 min—
Fri 13 NovNijmegen Heyendaal 08:020 min—
Thu 12 NovNijmegen Heyendaal 08:03+1 min—
Wed 11 NovNijmegen Heyendaal 08:19+16 min+17 min
Tue 10 NovNijmegen Heyendaal 08:02+4 min+4 min
Mon 9 NovNijmegen Heyendaal 08:03+1 min—
Sun 8 NovNijmegen Heyendaal 08:02Partial coverage0 min—
Sat 7 NovNijmegen Heyendaal 08:03Partial coverage0 min—
Fri 6 NovNijmegen Heyendaal 08:03No data—
Thu 5 NovNijmegen Heyendaal 08:04No data—
Wed 4 NovNijmegen Heyendaal 08:04+2 min+2 min
Tue 3 NovNijmegen Heyendaal 08:030 min—
Mon 2 NovNijmegen Heyendaal 08:03No data—
Fri 30 OctNijmegen Heyendaal 08:020 min—
Thu 29 OctNijmegen Heyendaal 08:040 min—
Wed 28 OctNijmegen Heyendaal 08:030 min—
Tue 27 OctNijmegen Heyendaal 08:020 min—
Mon 26 OctNijmegen Heyendaal 08:020 min—
Fri 23 OctTegelen 07:06+1 min—
Thu 22 OctTegelen 07:08+3 min+3 min
Wed 21 OctTegelen 07:05+2 min+2 min
Tue 20 OctTegelen 07:06+1 min—
Mon 19 OctTegelen 07:06+1 min+1 min
Fri 16 OctNijmegen Heyendaal 08:040 min—
Thu 15 OctNijmegen Heyendaal 08:040 min—
Tue 13 OctNijmegen Heyendaal 08:030 min—
Mon 12 OctNijmegen Heyendaal 08:040 min—
Sun 11 OctNijmegen Heyendaal 08:02Partial coverage0 min—
Sat 10 OctNijmegen Heyendaal 08:02Partial coverage0 min—
Fri 9 OctNijmegen Heyendaal 08:03+1 min—