Train NS 3250 Arnhem Centraal – Rotterdam Centraal

Arnhem Centraal 14:51 → Rotterdam Centraal 16:57 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 17:04 +3 min

  1. Arnhem Centraal14:51
  2. Veenendaal-De Klomp15:07
  3. Amsterdam Bijlmer ArenA15:48
  4. Schiphol Airport16:03
  5. Den Haag Laan v NOI16:34
  6. Schiedam Centrum16:52
  7. Rotterdam Centraal16:57

Next service: tomorrow 14:51 from Arnhem Centraal · Tue 10 Nov

Next departure 14:51 tomorrow · Arnhem Centraal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 4 full · 5 partial · 8 no data
On-time · 90 days
83%
10/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
+3min
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

  • Thu 8 Oct Max en route +4 min · last fix heading to Schiedam Centrum +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Schiedam Centrum +3 min

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 83% · 10
  • 3–10 min 17% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=2
  • 75% T n=4
  • — 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
14:51on time on time
15:01— —
15:07— —
15:26 / 15:31— —
15:48— —
15:54 / 15:57— —
16:03 / 16:05— —
16:22 / 16:24— —
16:34— —
16:36 / 16:38— —
16:44— —
16:52— —
16: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 17:04Partial coverage+3 min+3 min
Thu 5 NovSchiedam Centrum 17:04No data—
Wed 4 NovSchiedam Centrum 17:04Partial coverage0 min—
Tue 3 NovSchiedam Centrum 17:05No data—
Mon 2 NovSchiedam Centrum 17:24No data—
Thu 29 OctSchiedam Centrum 17:060 min—
Wed 28 OctSchiedam Centrum 17:07No data—
Tue 27 OctSchiedam Centrum 17:060 min—
Mon 26 OctSchiedam Centrum 17:07No data—
Thu 22 OctDen Haag Laan v NOI 16:480 min—
Wed 21 OctDen Haag Laan v NOI 16:47No data—
Tue 20 OctDen Haag Laan v NOI 16:470 min—
Mon 19 OctSchiedam Centrum 17:10Partial coverage0 min—
Thu 15 OctSchiedam Centrum 17:13Partial coverage0 min—
Wed 14 OctSchiedam Centrum 17:08No data—
Tue 13 OctSchiedam Centrum 17:09No data—
Mon 12 OctSchiedam Centrum 17:06Partial coverage0 min—
Thu 8 OctSchiedam Centrum 17:06Partial coverage+4 min+4 min
Wed 7 OctSchiedam Centrum 17:09Partial coverage+2 min+4 min
Tue 6 OctSchiedam Centrum 17:07Partial coverage0 min+2 min
Thu 1 OctSchiedam Centrum 17:06No data—
Wed 30 SeptSchiedam Centrum 17:09No data—
Tue 29 SeptSchiedam Centrum 17:06No data—
Mon 28 SeptSchiedam Centrum 17:06No data—
Thu 24 SeptSchiedam Centrum 17:06No data—
Wed 23 SeptSchiedam Centrum 17:04No data—
Tue 22 SeptSchiedam Centrum 17:06No data—
Mon 21 SeptSchiedam Centrum 17:06No data—
Thu 17 SeptSchiedam Centrum 17:06No data—
Wed 16 SeptSchiedam Centrum 17:08No data—