Train NS 3230 Arnhem Centraal – Rotterdam Centraal

Arnhem Centraal 09:51 → Rotterdam Centraal 11:57 Mon, Tue, Wed, Thu 2 h 06 min · 13 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 09:51 from Arnhem Centraal · Mon 9 Nov

Next departure 09:51 Monday · Arnhem Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 4 full · 3 partial · 10 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 24 full · 5 partial · 17 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: +2 min

Last 30 days

Arrival delay at Rotterdam 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

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

  • Early 3% · 1
  • On time 97% · 28
  • 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=7
  • 100% W n=6
  • 100% T n=6
  • 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, 29 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
09:51on time on time
10:01≈ on time ≈ on time
10:07≈ on time ≈ on time
10:26 / 10:31≈ on time ≈ on time
10:48≈ on time ≈ on time
10:54 / 10:57≈ on time ≈ on time
11:03 / 11:05≈ on time ≈ on time
11:22 / 11:24≈ on time ≈ on time
11:34≈ on time ≈ on time
11:36 / 11:38≈ on time ≈ on time
11:44≈ on time ≈ on time
11:52≈ on time ≈ on time
11:57on 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
Thu 5 NovSchiedam Centrum 12:08No data—
Wed 4 NovSchiedam Centrum 12:07Partial coverage+2 min+2 min
Tue 3 NovSchiedam Centrum 12:08No data—
Mon 2 NovSchiedam Centrum 12:07No data—
Thu 29 OctSchiedam Centrum 12:070 min—
Wed 28 OctSchiedam Centrum 12:08No data—
Tue 27 OctSchiedam Centrum 12:070 min—
Mon 26 OctDelft 12:19No data—
Thu 22 OctDen Haag Laan v NOI 11:55No data—
Wed 21 OctDen Haag Laan v NOI 11:500 min—
Tue 20 OctDen Haag Laan v NOI 11:500 min—
Mon 19 OctSchiedam Centrum 12:07Partial coverage0 min—
Thu 15 OctSchiedam Centrum 12:07No data—
Wed 14 OctSchiedam Centrum 12:07No data—
Tue 13 OctSchiedam Centrum 12:07No data—
Mon 12 OctSchiedam Centrum 12:07No data—
Thu 8 OctSchiedam Centrum 12:07Partial coverage+3 min+3 min
Wed 7 OctSchiedam Centrum 12:09Partial coverage0 min—
Tue 6 OctSchiedam Centrum 12:07Partial coverage0 min+2 min
Thu 1 OctSchiedam Centrum 12:06No data—
Wed 30 SeptSchiedam Centrum 12:08No data—
Tue 29 SeptSchiedam Centrum 12:06No data—
Mon 28 SeptSchiedam Centrum 12:07No data—
Thu 24 SeptSchiedam Centrum 12:07No data—
Wed 23 SeptSchiedam Centrum 12:06No data—
Tue 22 SeptSchiedam Centrum 12:11No data—
Mon 21 SeptAmsterdam Zuid 14:300 min+6 min
Thu 17 SeptSchiphol Airport 18:160 min+9 min
Wed 16 SeptAmsterdam Zuid 19:410 min+4 min
Tue 15 SeptSchiedam Centrum 12:060 min—