Train NS 3251 Rotterdam Centraal – Arnhem Centraal

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

It does not run today

Last recorded run: Thursday 12 November +1 min

Next service: tomorrow 13:33 from Rotterdam Centraal · Mon 16 Nov

Next departure 13:33 tomorrow · Rotterdam Centraal
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 4 full · 6 partial · 6 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 4 full · 10 partial · 35 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: +3 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

Worst days

  • Wed 4 Nov Max en route +4 min · last fix heading to Ede-Wageningen +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Ede-Wageningen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 67% W n=3
  • 100% T n=4
  • — 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, 14 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:33on time on time
13:38— —
13:45— —
13:52 / 13:54— —
13:57— —
14:06 / 14:08— —
14:23 / 14:26— —
14:32 / 14:36— —
14:41 / 14:42— —
14:58 / 15:07— —
15:25— —
15:31— —
15:41— —

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