Train NS 3235 Rotterdam Centraal – Arnhem Centraal

Rotterdam Centraal 09:33 → Arnhem Centraal 11:41 Mon, Tue, Wed, Thu 2 h 08 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 09:33 from Rotterdam Centraal · Tue 10 Nov

Next departure 09:33 today · Rotterdam Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 5 full · 3 partial · 9 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 11
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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:33on time on time
09:38≈ on time ≈ on time
09:45≈ on time ≈ on time
09:52 / 09:54≈ on time ≈ on time
09:57≈ on time ≈ on time
10:06 / 10:09≈ on time ≈ on time
10:24 / 10:26≈ on time ≈ on time
10:32 / 10:36≈ on time ≈ on time
10:41 / 10:42≈ on time ≈ on time
10:58 / 11:06≈ on time ≈ on time
11:24≈ on time ≈ on time
11:31≈ on time ≈ on time
11:41on time on time

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
Mon 9 NovEde-Wageningen 11:44Partial coverage0 min—
Thu 5 NovEde-Wageningen 11:44No data—
Wed 4 NovEde-Wageningen 11:44Partial coverage0 min+2 min
Tue 3 NovEde-Wageningen 11:44Partial coverage0 min—
Mon 2 NovEde-Wageningen 11:44No data—
Thu 29 OctVeenendaal-De Klomp 11:410 min—
Wed 28 OctVeenendaal-De Klomp 11:380 min—
Tue 27 OctVeenendaal-De Klomp 11:380 min—
Mon 26 OctVeenendaal-De Klomp 11:38No data—
Thu 22 OctAmsterdam Bijlmer ArenA 11:010 min—
Wed 21 OctAmsterdam Bijlmer ArenA 10:56No data—
Tue 20 OctAmsterdam Bijlmer ArenA 10:59No data—
Mon 19 OctEde-Wageningen 11:460 min—
Thu 15 OctEde-Wageningen 11:45No data—
Wed 14 OctEde-Wageningen 11:45No data—
Tue 13 OctEde-Wageningen 11:46No data—
Mon 12 OctEde-Wageningen 11:45No data—
Thu 8 OctEde-Wageningen 11:47Partial coverage+2 min+2 min
Wed 7 OctEde-Wageningen 12:00Partial coverage0 min—
Tue 6 OctEde-Wageningen 11:45Partial coverage0 min—
Thu 1 OctEde-Wageningen 11:45No data—
Wed 30 SeptEde-Wageningen 11:46No data—
Tue 29 SeptEde-Wageningen 11:45No data—
Mon 28 SeptEde-Wageningen 11:45No data—
Thu 24 SeptEde-Wageningen 11:45No data—
Wed 23 SeptEde-Wageningen 11:45No data—
Tue 22 SeptEde-Wageningen 11:45No data—
Mon 21 SeptEde-Wageningen 11:45No data—
Thu 17 SeptEde-Wageningen 11:45No data—
Wed 16 SeptEde-Wageningen 11:46No data—