Train NS 3241 Rotterdam Centraal – Arnhem Centraal

Rotterdam Centraal 11:03 → Arnhem Centraal 13: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 13:12 0 min

  1. Rotterdam Centraal11:03
  2. Delft11:15
  3. Den Haag Laan v NOI11:27
  4. Schiphol Airport11:53
  5. Amsterdam Bijlmer ArenA12:11
  6. Ede-Wageningen12:58
  7. Arnhem Centraal13:08

Next service: tomorrow 11:03 from Rotterdam Centraal · Wed 11 Nov

Next departure 11:03 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 7 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 33 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 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, 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
11:03on time on time
11:08≈ on time ≈ on time
11:15≈ on time ≈ on time
11:22 / 11:24≈ on time ≈ on time
11:27≈ on time ≈ on time
11:36 / 11:38≈ on time ≈ on time
11:53 / 11:56≈ on time ≈ on time
12:02 / 12:06≈ on time ≈ on time
12:11 / 12:12≈ on time ≈ on time
12:28 / 12:34≈ on time ≈ on time
12:52≈ on time ≈ on time
12:58≈ on time ≈ on time
13: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
Tue 10 NovEde-Wageningen 13:12Partial coverage0 min—
Mon 9 NovEde-Wageningen 13:14Partial coverage+1 min+2 min
Thu 5 NovEde-Wageningen 13:39No data—
Wed 4 NovEde-Wageningen 13:14Partial coverage+3 min+4 min
Tue 3 NovEde-Wageningen 13:12No data—
Mon 2 NovRotterdam Centraal 13:09Partial coverage0 min—
Thu 29 OctVeenendaal-De Klomp 13:090 min—
Wed 28 OctVeenendaal-De Klomp 13:080 min—
Tue 27 OctVeenendaal-De Klomp 13:120 min—
Mon 26 OctVeenendaal-De Klomp 13:090 min—
Thu 22 OctAmsterdam Bijlmer ArenA 12:28No data—
Wed 21 OctAmsterdam Bijlmer ArenA 12:29No data—
Tue 20 OctAmsterdam Bijlmer ArenA 12:290 min—
Mon 19 OctEde-Wageningen 13:12Partial coverage0 min—
Thu 15 OctEde-Wageningen 13:12Partial coverage0 min—
Wed 14 OctEde-Wageningen 13:12No data—
Tue 13 OctEde-Wageningen 13:13No data—
Mon 12 OctEde-Wageningen 13:13No data—
Thu 8 OctDen Haag HS 13:27Partial coverage0 min+9 min
Wed 7 OctEde-Wageningen 13:19Partial coverage0 min—
Tue 6 OctEde-Wageningen 13:12Partial coverage0 min—
Thu 1 OctEde-Wageningen 13:12No data—
Wed 30 SeptEde-Wageningen 13:12No data—
Tue 29 SeptEde-Wageningen 13:14No data—
Mon 28 SeptEde-Wageningen 13:12No data—
Thu 24 SeptEde-Wageningen 13:12No data—
Wed 23 SeptEde-Wageningen 13:13No data—
Tue 22 SeptEde-Wageningen 13:12No data—
Mon 21 SeptEde-Wageningen 13:12No data—
Thu 17 SeptEde-Wageningen 13:12No data—