Train NS 3237 Rotterdam Centraal – Arnhem Centraal

Rotterdam Centraal 10:03 → Arnhem Centraal 12: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 12:14 +2 min

  1. Rotterdam Centraal10:03
  2. Delft10:15
  3. Den Haag Laan v NOI10:27
  4. Schiphol Airport10:53
  5. Amsterdam Bijlmer ArenA11:11
  6. Ede-Wageningen11:58
  7. Arnhem Centraal12:08

Next service: Monday 10:03 from Rotterdam Centraal · Mon 23 Nov

Next departure 10:03 Monday · Rotterdam Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 5 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 33 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

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

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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • — 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:03on time on time
10:08— —
10:15— —
10:22 / 10:24— —
10:27— —
10:36 / 10:38— —
10:53 / 10:56— —
11:02 / 11:06— —
11:11 / 11:12— —
11:28 / 11:34— —
11:52— —
11:58— —
12:08— —

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 19 NovEde-Wageningen 12:14Partial coverage+2 min+2 min
Wed 18 NovEde-Wageningen 12:18Partial coverage+3 min+3 min
Tue 17 NovEde-Wageningen 12:12Partial coverage0 min—
Mon 16 NovEde-Wageningen 12:14Partial coverage0 min—
Thu 12 NovEde-Wageningen 12:12Partial coverage0 min—
Wed 11 NovEde-Wageningen 12:14Partial coverage+1 min+2 min
Tue 10 NovEde-Wageningen 12:12Partial coverage+1 min+1 min
Mon 9 NovEde-Wageningen 12:18Partial coverage+4 min+5 min
Thu 5 NovEde-Wageningen 12:12No data—
Wed 4 NovEde-Wageningen 12:13Partial coverage+1 min—
Tue 3 NovEde-Wageningen 12:19No data—
Mon 2 NovEde-Wageningen 12:18Partial coverage0 min—
Thu 29 OctVeenendaal-De Klomp 12:080 min—
Wed 28 OctVeenendaal-De Klomp 12:10No data—
Tue 27 OctVeenendaal-De Klomp 12:080 min—
Mon 26 OctVeenendaal-De Klomp 12:08No data—
Thu 22 OctAmsterdam Bijlmer ArenA 11:290 min—
Wed 21 OctAmsterdam Bijlmer ArenA 11:26No data—
Tue 20 OctAmsterdam Bijlmer ArenA 11:290 min—
Mon 19 OctEde-Wageningen 12:12Partial coverage0 min—
Thu 15 OctEde-Wageningen 12:16No data—
Wed 14 OctEde-Wageningen 12:13Partial coverage0 min—
Tue 13 OctEde-Wageningen 12:13No data—
Mon 12 OctEde-Wageningen 12:12No data—
Thu 8 OctEde-Wageningen 12:13Partial coverage+1 min+1 min
Wed 7 OctEde-Wageningen 12:16Partial coverage+2 min+3 min
Tue 6 OctEde-Wageningen 12:13Partial coverage0 min—
Thu 1 OctEde-Wageningen 12:12No data—
Wed 30 SeptEde-Wageningen 12:12No data—
Tue 29 SeptEde-Wageningen 12:13No data—