Train NS 3240 Arnhem Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Schiedam Centrum at 14:49 No data

  1. Arnhem Centraal12:21
  2. Veenendaal-De Klomp12:37
  3. Amsterdam Bijlmer ArenA13:18
  4. Schiphol Airport13:33
  5. Leiden Centraal13:52
  6. Schiedam Centrum14:22
  7. Rotterdam Centraal14:27

Next service: Monday 12:21 from Arnhem Centraal · Mon 9 Nov

Next departure 12:21 Monday · Arnhem Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 10 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 2 full · 7 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 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 (12 stops).

Last 90 days, 9 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
12:21on time on time
12:31— —
12:37— —
12:56 / 13:01— —
13:18— —
13:24 / 13:27— —
13:33 / 13:35— —
13:52 / 13:54— —
14:04— —
14:06 / 14:08— —
14:22— —
14: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 14:49No data—
Wed 4 NovSchiedam Centrum 14:37Partial coverage+1 min—
Tue 3 NovSchiedam Centrum 14:37No data—
Mon 2 NovSchiedam Centrum 14:37Partial coverage0 min—
Thu 29 OctSchiedam Centrum 14:360 min—
Wed 28 OctSchiedam Centrum 14:37No data—
Tue 27 OctSchiedam Centrum 14:370 min—
Mon 26 OctSchiedam Centrum 14:37No data—
Thu 22 OctDen Haag Laan v NOI 14:19No data—
Wed 21 OctDen Haag Laan v NOI 14:18No data—
Tue 20 OctDen Haag Laan v NOI 14:18No data—
Mon 19 OctSchiedam Centrum 14:37Partial coverage0 min—
Thu 15 OctSchiedam Centrum 14:37No data—
Wed 14 OctSchiedam Centrum 14:37Partial coverage0 min—
Tue 13 OctSchiedam Centrum 14:37No data—
Mon 12 OctSchiedam Centrum 14:37No data—
Thu 8 OctSchiedam Centrum 14:36Partial coverage+1 min+2 min
Wed 7 OctSchiedam Centrum 14:37Partial coverage0 min+2 min
Tue 6 OctSchiedam Centrum 14:37Partial coverage0 min—
Thu 1 OctSchiedam Centrum 14:37No data—
Wed 30 SeptSchiedam Centrum 14:37No data—
Tue 29 SeptSchiedam Centrum 14:37No data—
Mon 28 SeptSchiedam Centrum 14:38No data—
Thu 24 SeptSchiedam Centrum 14:37No data—
Wed 23 SeptSchiedam Centrum 14:37No data—
Tue 22 SeptSchiedam Centrum 14:37No data—
Mon 21 SeptSchiedam Centrum 14:37No data—
Thu 17 SeptSchiedam Centrum 14:37No data—
Wed 16 SeptSchiedam Centrum 14:38No data—
Tue 15 SeptSchiedam Centrum 14:36No data—