Train NS 3246 Arnhem Centraal – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 13:51 from Arnhem Centraal · Tue 10 Nov

Next departure 13:51 today · Arnhem Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 9 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 3 full · 8 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
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

Worst days

  • Wed 7 Oct Max en route +10 min · last fix heading to Schiedam Centrum +9 min
  • Tue 6 Oct Max en route +7 min · last fix heading to Schiedam Centrum +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 9
  • 3–10 min 18% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 50% T n=2
  • 75% W n=4
  • 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, 11 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
13:51on time on time
14:01— —
14:07— —
14:26 / 14:31— —
14:48— —
14:54 / 14:57— —
15:03 / 15:05— —
15:22 / 15:24— —
15:34— —
15:36 / 15:38— —
15:44— —
15:52— —
15:57— —

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
Mon 9 NovSchiedam Centrum 16:07Partial coverage0 min+2 min
Thu 5 NovSchiedam Centrum 16:05No data—
Wed 4 NovSchiedam Centrum 16:08Partial coverage+2 min+2 min
Tue 3 NovSchiedam Centrum 16:04No data—
Mon 2 NovSchiedam Centrum 16:07No data—
Thu 29 OctSchiedam Centrum 16:070 min—
Wed 28 OctSchiedam Centrum 16:070 min—
Tue 27 OctSchiedam Centrum 16:080 min—
Mon 26 OctSchiedam Centrum 16:07No data—
Thu 22 OctDen Haag Laan v NOI 15:54No data—
Wed 21 OctDen Haag Laan v NOI 15:56No data—
Tue 20 OctDen Haag Laan v NOI 15:48No data—
Mon 19 OctSchiedam Centrum 16:08Partial coverage0 min—
Thu 15 OctSchiedam Centrum 16:07No data—
Wed 14 OctSchiedam Centrum 16:11Partial coverage0 min—
Tue 13 OctSchiedam Centrum 16:07No data—
Mon 12 OctSchiedam Centrum 16:06Partial coverage0 min—
Thu 8 OctSchiedam Centrum 16:07Partial coverage0 min—
Wed 7 OctSchiedam Centrum 16:16Partial coverage+9 min+10 min
Tue 6 OctSchiedam Centrum 16:07Partial coverage+7 min+7 min
Thu 1 OctSchiedam Centrum 16:08No data—
Wed 30 SeptSchiedam Centrum 16:07No data—
Tue 29 SeptSchiedam Centrum 16:07No data—
Mon 28 SeptSchiedam Centrum 16:06No data—
Thu 24 SeptSchiedam Centrum 16:07No data—
Wed 23 SeptSchiedam Centrum 16:06No data—
Tue 22 SeptSchiedam Centrum 16:07No data—
Mon 21 SeptSchiedam Centrum 16:07No data—
Thu 17 SeptSchiedam Centrum 16:07No data—
Wed 16 SeptSchiedam Centrum 16:20No data—