Train Arriva 32255 Nijmegen – Venlo

Nijmegen 15:38 → Venlo 16:31 Daily 0 h 53 min · 9 stops Arriva

Running now · updated 16:14

Position estimated from the timetable

Heading to Venlo +2 min

Estimated arrival at Venlo 16:33 16:31 · 87 km/h

  1. Nijmegen15:38
  2. Nijmegen Heyendaal15:41
  3. Cuijk15:50
  4. Boxmeer15:59
  5. Vierlingsbeek16:07
  6. Blerick16:28
  7. Venlo16:31

Today it is running worse than usual: typical arrival delay is 0 min; 95% of the last 19 runs arrived on time.

On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 60 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Swalmen +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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 10Today
15:38on time on time
15:41≈ on time ≈ on time
15:46≈ on time ≈ on time
15:50 / 15:52≈ on time ≈ +1 min
15:59 / 16:02≈ on time ≈ +1 min
16:07 / 16:08≈ on time ≈ +1 min
16:14 / 16:15≈ on time ≈ +2 min
16:28≈ +1 min ≈ +2 min
16:31+1 min +2 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
Wed 18 NovVierlingsbeek 16:09Partial coverage+1 min+1 min
Tue 17 NovSwalmen 17:04+1 min—
Mon 16 NovSwalmen 17:08+2 min+2 min
Sun 15 NovSwalmen 17:07+3 min+4 min
Sat 14 NovSwalmen 17:040 min+1 min
Fri 13 NovSwalmen 17:040 min+1 min
Thu 12 NovSwalmen 17:04+1 min—
Wed 11 NovSwalmen 17:04+2 min+2 min
Tue 10 NovSwalmen 17:09+5 min+6 min
Mon 9 NovSwalmen 17:04+1 min+2 min
Sun 8 NovSwalmen 17:050 min+1 min
Sat 7 NovSwalmen 17:04+1 min—
Fri 6 NovSwalmen 17:04No data—
Thu 5 NovSwalmen 17:04No data—
Wed 4 NovSwalmen 17:040 min—
Tue 3 NovSwalmen 17:040 min—
Mon 2 NovSwalmen 17:070 min—
Sun 1 NovSwalmen 17:04No data—
Sat 31 OctSwalmen 17:040 min—
Fri 30 OctSwalmen 17:05No data—
Thu 29 OctSwalmen 17:040 min—
Wed 28 OctSwalmen 17:050 min—
Tue 27 OctSwalmen 17:08No data—
Mon 26 OctSwalmen 17:04No data—
Sun 25 OctSwalmen 17:05No data—
Sat 24 OctSwalmen 17:04No data—
Fri 23 OctSwalmen 17:06No data—
Thu 22 OctSwalmen 17:05No data—
Wed 21 OctSwalmen 17:04No data—
Tue 20 OctSwalmen 17:040 min—