Train NS 3239 Rotterdam Centraal – Arnhem Centraal

Rotterdam Centraal 10:33 → Arnhem Centraal 12:38 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 12:43 +1 min

  1. Rotterdam Centraal10:33
  2. Delft10:45
  3. Den Haag Laan v NOI10:57
  4. Schiphol Airport11:23
  5. Amsterdam Bijlmer ArenA11:41
  6. Ede-Wageningen12:28
  7. Arnhem Centraal12:38

Next service: tomorrow 10:33 from Rotterdam Centraal · Wed 18 Nov

Next departure 10:33 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 5 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 4 full · 15 partial · 32 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 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

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

  • Early 0% · 0
  • On time 100% · 19
  • 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=5
  • 100% W n=4
  • 100% T n=6
  • — 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, 19 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
10:33on time on time
10:38— —
10:45— —
10:52 / 10:54— —
10:57— —
11:06 / 11:08— —
11:23 / 11:26— —
11:32 / 11:36— —
11:41 / 11:42— —
11:58 / 12:04— —
12:22— —
12:28— —
12:38— —

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