Train NS 3257 Rotterdam Centraal – Arnhem Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:03 from Rotterdam Centraal · Thu 5 Nov

Next departure 15:03 today · Rotterdam Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 8 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 24 full · 7 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Thu 1 Oct Max en route +15 min · last fix heading to Amsterdam Zuid +12 min
  • Tue 8 Sept Max en route +10 min · last fix heading to Amsterdam Zuid +9 min

Distribution · 90 days

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

  • Early 10% · 3
  • On time 84% · 26
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 80% T n=5
  • 100% W n=7
  • 86% T n=7
  • 100% F n=1
  • 100% S n=1
  • 100% S n=1

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 stops).

Last 90 days, 31 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
15:03on time on time
15:08≈ on time ≈ on time
15:15≈ on time ≈ on time
15:22 / 15:24≈ on time ≈ on time
15:27≈ on time ≈ on time
15:36 / 15:38≈ on time ≈ on time
15:53 / 15:56≈ on time ≈ on time
16:02 / 16:06≈ on time ≈ on time
16:11 / 16:12≈ on time ≈ on time
16:28 / 16:34≈ on time ≈ on time
16:52≈ on time ≈ on time
16:58≈ on time ≈ on time
17: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 4 NovEde-Wageningen 17:18Partial coverage0 min—
Tue 3 NovEde-Wageningen 17:12No data—
Mon 2 NovEde-Wageningen 17:18No data—
Thu 29 OctVeenendaal-De Klomp 17:060 min—
Wed 28 OctVeenendaal-De Klomp 17:060 min—
Tue 27 OctVeenendaal-De Klomp 17:30No data—
Mon 26 OctVeenendaal-De Klomp 17:060 min—
Thu 22 OctAmsterdam Bijlmer ArenA 16:29No data—
Wed 21 OctAmsterdam Bijlmer ArenA 16:29No data—
Tue 20 OctAmsterdam Bijlmer ArenA 16:41No data—
Mon 19 OctEde-Wageningen 17:13Partial coverage0 min—
Thu 15 OctEde-Wageningen 17:13Partial coverage0 min—
Wed 14 OctEde-Wageningen 17:12No data—
Tue 13 OctEde-Wageningen 17:14No data—
Mon 12 OctEde-Wageningen 17:13Partial coverage0 min—
Thu 8 OctEde-Wageningen 17:12Partial coverage0 min—
Wed 7 OctEde-Wageningen 17:12Partial coverage0 min—
Tue 6 OctEde-Wageningen 17:12Partial coverage0 min—
Thu 1 OctAmsterdam Zuid 19:25+12 min+15 min
Wed 30 SeptEde-Wageningen 17:12No data—
Tue 29 SeptAmsterdam Zuid 18:370 min+2 min
Mon 28 SeptEde-Wageningen 17:130 min—
Thu 24 SeptEde-Wageningen 17:07No data—
Wed 23 SeptAmsterdam Zuid 19:030 min+3 min
Tue 22 SeptEde-Wageningen 17:12No data—
Mon 21 SeptEde-Wageningen 17:12No data—
Thu 17 SeptAmsterdam Zuid 00:020 min+10 min
Wed 16 SeptSchiphol Airport 17:560 min+6 min
Tue 15 SeptAmsterdam Zuid 18:42−2 min+6 min
Mon 14 SeptSchiphol Airport 18:530 min—