Train NS 3225 Rotterdam Centraal – Arnhem Centraal

Rotterdam Centraal 07:03 → Arnhem Centraal 09:08 Mon, Tue, Wed, Thu 2 h 05 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Ede-Wageningen at 09:14 +2 min

  1. Rotterdam Centraal07:03
  2. Delft07:15
  3. Den Haag Laan v NOI07:27
  4. Schiphol Airport07:53
  5. Amsterdam Bijlmer ArenA08:11
  6. Ede-Wageningen08:58
  7. Arnhem Centraal09:08

Next service: tomorrow 07:03 from Rotterdam Centraal · Thu 12 Nov

Next departure 07:03 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 2 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 33 full · 1 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 6% · 2
  • On time 94% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=10
  • 100% W n=8
  • 100% T n=9
  • — 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, 34 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
07:03on time on time
07:08≈ on time ≈ on time
07:15≈ on time ≈ on time
07:22 / 07:24≈ on time ≈ on time
07:27≈ on time ≈ on time
07:36 / 07:38≈ on time ≈ on time
07:53 / 07:56≈ on time ≈ on time
08:02 / 08:06≈ on time ≈ on time
08:11 / 08:13≈ on time ≈ on time
08:29 / 08:34≈ on time ≈ on time
08:52≈ on time ≈ on time
08:58≈ on time ≈ on time
09:08on 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
Wed 11 NovEde-Wageningen 09:14Partial coverage+2 min+2 min
Tue 10 NovEde-Wageningen 09:13+2 min+2 min
Mon 9 NovEde-Wageningen 09:120 min—
Thu 5 NovEde-Wageningen 09:240 min—
Wed 4 NovEde-Wageningen 09:120 min—
Tue 3 NovEde-Wageningen 09:140 min—
Mon 2 NovEde-Wageningen 09:19No data—
Thu 29 OctVeenendaal-De Klomp 09:08+1 min+1 min
Wed 28 OctVeenendaal-De Klomp 09:080 min—
Tue 27 OctVeenendaal-De Klomp 09:080 min—
Mon 26 OctVeenendaal-De Klomp 09:110 min—
Thu 22 OctDen Haag HS 08:340 min—
Wed 21 OctAmsterdam Bijlmer ArenA 08:29No data—
Tue 20 OctAmsterdam Bijlmer ArenA 08:290 min—
Mon 19 OctEde-Wageningen 09:120 min—
Thu 15 OctEde-Wageningen 09:130 min—
Wed 14 OctEde-Wageningen 09:120 min—
Tue 13 OctEde-Wageningen 09:120 min—
Mon 12 OctEde-Wageningen 09:120 min—
Thu 8 OctEde-Wageningen 09:12+1 min+1 min
Wed 7 OctEde-Wageningen 09:120 min—
Tue 6 OctEde-Wageningen 09:120 min—
Thu 1 OctAmsterdam Zuid 20:05−4 min+1 min
Wed 30 SeptAmsterdam Zuid 18:060 min—
Tue 29 SeptAmsterdam Zuid 19:040 min+5 min
Mon 28 SeptEde-Wageningen 09:12No data—
Thu 24 SeptAmsterdam Zuid 00:340 min+14 min
Wed 23 SeptSchiphol Airport 11:240 min—
Tue 22 SeptAmsterdam Zuid 23:320 min+5 min
Mon 21 SeptAmsterdam Zuid 19:430 min+9 min