Train Arriva 32247 Nijmegen – Venlo

Nijmegen 13:38 → Venlo 14:31 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 13:38 from Nijmegen · Fri 20 Nov

Next departure 13:38 today · Nijmegen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 8 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 28 full · 2 partial · 57 no data
Typical delay
0min
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

  • Thu 12 Nov Max en route +6 min · last fix heading to Swalmen +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Swalmen +3 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 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 83% T n=6
  • 100% W n=5
  • 75% T n=4
  • 100% F n=2
  • 100% S n=4
  • 100% 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
13:38on time on time
13:41≈ on time ≈ on time
13:46≈ on time ≈ on time
13:50 / 13:52≈ on time ≈ +1 min
13:59 / 14:02≈ on time ≈ +1 min
14:07 / 14:08≈ on time ≈ +1 min
14:14 / 14:15≈ on time ≈ +1 min
14:28≈ on time ≈ +2 min
14:31on time +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
Thu 19 NovBlerick 14:43Partial coverage+1 min—
Wed 18 NovBlerick 14:44Partial coverage+2 min+2 min
Tue 17 NovSwalmen 15:07+2 min+3 min
Mon 16 NovSwalmen 15:05+1 min+2 min
Sun 15 NovSwalmen 15:04+1 min+2 min
Sat 14 NovSwalmen 15:07+2 min+3 min
Fri 13 NovSwalmen 15:040 min—
Thu 12 NovSwalmen 15:09+4 min+6 min
Wed 11 NovSwalmen 15:040 min+2 min
Tue 10 NovSwalmen 15:08+3 min+4 min
Mon 9 NovSwalmen 15:040 min+1 min
Sun 8 NovSwalmen 15:040 min—
Sat 7 NovSwalmen 15:040 min+1 min
Fri 6 NovSwalmen 15:04No data—
Thu 5 NovSwalmen 15:04No data—
Wed 4 NovSwalmen 15:040 min+1 min
Tue 3 NovSwalmen 15:040 min—
Mon 2 NovSwalmen 15:040 min—
Sun 1 NovSwalmen 15:06+1 min—
Sat 31 OctSwalmen 15:050 min+1 min
Fri 30 OctSwalmen 15:05No data—
Thu 29 OctSwalmen 15:040 min—
Wed 28 OctSwalmen 15:180 min—
Tue 27 OctSwalmen 15:060 min—
Mon 26 OctSwalmen 15:04No data—
Sun 25 OctSwalmen 15:05No data—
Sat 24 OctSwalmen 15:04No data—
Fri 23 OctSwalmen 15:04No data—
Thu 22 OctSwalmen 15:04No data—
Wed 21 OctSwalmen 15:05No data—