Train NS 3228 Arnhem Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Schiedam Centrum at 11:37 0 min

  1. Arnhem Centraal09:21
  2. Veenendaal-De Klomp09:37
  3. Amsterdam Bijlmer ArenA10:18
  4. Schiphol Airport10:33
  5. Den Haag Laan v NOI11:04
  6. Schiedam Centrum11:22
  7. Rotterdam Centraal11:27

Next service: tomorrow 09:21 from Arnhem Centraal · Wed 11 Nov

Next departure 09:21 tomorrow · Arnhem Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 9 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 35 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=4
  • 100% W n=3
  • 100% T n=2
  • — 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
09:21on time on time
09:31— —
09:37— —
09:56 / 10:01— —
10:18— —
10:24 / 10:27— —
10:33 / 10:35— —
10:52 / 10:54— —
11:04— —
11:06 / 11:08— —
11:14— —
11:22— —
11: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
Tue 10 NovSchiedam Centrum 11:37Partial coverage0 min—
Mon 9 NovSchiedam Centrum 11:37Partial coverage0 min—
Thu 5 NovSchiedam Centrum 11:37No data—
Wed 4 NovSchiedam Centrum 11:37Partial coverage0 min—
Tue 3 NovSchiedam Centrum 11:37No data—
Mon 2 NovSchiedam Centrum 11:37No data—
Thu 29 OctSchiedam Centrum 11:370 min—
Wed 28 OctSchiedam Centrum 11:36No data—
Tue 27 OctSchiedam Centrum 11:370 min—
Mon 26 OctSchiedam Centrum 11:370 min—
Thu 22 OctDen Haag Laan v NOI 11:17No data—
Wed 21 OctDen Haag Laan v NOI 11:18No data—
Tue 20 OctDen Haag Laan v NOI 11:170 min—
Mon 19 OctSchiedam Centrum 11:38Partial coverage0 min—
Thu 15 OctSchiedam Centrum 11:37No data—
Wed 14 OctSchiedam Centrum 11:37Partial coverage0 min—
Tue 13 OctSchiedam Centrum 11:37No data—
Mon 12 OctSchiedam Centrum 11:37No data—
Thu 8 OctSchiedam Centrum 11:37Partial coverage+1 min—
Wed 7 OctSchiedam Centrum 12:01Partial coverage0 min—
Tue 6 OctSchiedam Centrum 11:37Partial coverage+3 min+3 min
Thu 1 OctSchiedam Centrum 11:37No data—
Wed 30 SeptSchiedam Centrum 11:39No data—
Tue 29 SeptSchiedam Centrum 11:37No data—
Mon 28 SeptSchiedam Centrum 11:37No data—
Thu 24 SeptSchiedam Centrum 11:37No data—
Wed 23 SeptSchiedam Centrum 11:37No data—
Tue 22 SeptSchiedam Centrum 11:37No data—
Mon 21 SeptSchiedam Centrum 11:37No data—
Thu 17 SeptSchiedam Centrum 11:37No data—