Train NS 3236 Arnhem Centraal – Rotterdam Centraal

Arnhem Centraal 11:21 → Rotterdam Centraal 13:27 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 11:21 from Arnhem Centraal · Mon 9 Nov

Next departure 11:21 Monday · Arnhem Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 7 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 34 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 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=4
  • 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, 12 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:21on time on time
11:31— —
11:37— —
11:56 / 12:01— —
12:18— —
12:24 / 12:27— —
12:33 / 12:35— —
12:52 / 12:54— —
13:04— —
13:06 / 13:08— —
13:14— —
13:22— —
13:27— —

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 13:37No data—
Wed 4 NovSchiedam Centrum 13:37Partial coverage0 min—
Tue 3 NovSchiedam Centrum 13:34No data—
Mon 2 NovSchiedam Centrum 13:34Partial coverage0 min—
Thu 29 OctSchiedam Centrum 13:370 min—
Wed 28 OctSchiedam Centrum 13:370 min—
Tue 27 OctSchiedam Centrum 13:39No data—
Mon 26 OctSchiedam Centrum 13:37No data—
Thu 22 OctDen Haag Laan v NOI 13:180 min—
Wed 21 OctDen Haag Laan v NOI 13:18No data—
Tue 20 OctDen Haag Laan v NOI 13:210 min—
Mon 19 OctSchiedam Centrum 13:37Partial coverage0 min—
Thu 15 OctSchiedam Centrum 13:37No data—
Wed 14 OctSchiedam Centrum 13:37Partial coverage0 min—
Tue 13 OctSchiedam Centrum 13:37No data—
Mon 12 OctSchiedam Centrum 13:37Partial coverage0 min—
Thu 8 OctSchiedam Centrum 13:37Partial coverage0 min+2 min
Wed 7 OctSchiedam Centrum 13:37Partial coverage0 min—
Tue 6 OctSchiedam Centrum 13:37Partial coverage0 min—
Thu 1 OctSchiedam Centrum 13:37No data—
Wed 30 SeptSchiedam Centrum 13:37No data—
Tue 29 SeptSchiedam Centrum 13:38No data—
Mon 28 SeptSchiedam Centrum 13:40No data—
Thu 24 SeptSchiedam Centrum 13:37No data—
Wed 23 SeptSchiedam Centrum 13:38No data—
Tue 22 SeptSchiedam Centrum 13:38No data—
Mon 21 SeptSchiedam Centrum 13:39No data—
Thu 17 SeptSchiedam Centrum 13:37No data—
Wed 16 SeptSchiedam Centrum 13:38No data—
Tue 15 SeptSchiedam Centrum 13:36No data—