Train NS 3260 Arnhem Centraal – Rotterdam Centraal

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

Running now · updated 17:27

Heading to Rotterdam Centraal No data

Estimated arrival at Rotterdam Centraal 19:27 · 97 km/h

  1. Arnhem Centraal17:21
  2. Veenendaal-De Klomp17:37
  3. Amsterdam Bijlmer ArenA18:18
  4. Schiphol Airport18:33
  5. Den Haag Laan v NOI19:04
  6. Delft19:14
  7. Rotterdam Centraal19:27
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 8 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 8 full · 3 partial · 35 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=2
  • 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, 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 10Today
17:21on time on time
17:31≈ on time ≈ on time
17:37≈ on time ≈ on time
17:56 / 18:01≈ on time ≈ on time
18:18≈ on time ≈ on time
18:24 / 18:27≈ on time ≈ on time
18:33 / 18:35≈ on time ≈ +1 min
18:52 / 18:54≈ on time ≈ +1 min
19:04≈ on time ≈ +1 min
19:06 / 19:08≈ on time ≈ +1 min
19:14≈ on time ≈ +1 min
19:22≈ on time ≈ +1 min
19:27on time +1 min

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 NovEde-Wageningen 17:24No data—
Wed 4 NovUtrecht Centraal 19:29No data—
Tue 3 NovUtrecht Centraal 19:28No data—
Mon 2 NovUtrecht Centraal 19:28Partial coverage0 min—
Thu 29 OctUtrecht Centraal 19:290 min—
Wed 28 OctUtrecht Centraal 18:25No data—
Tue 27 OctUtrecht Centraal 19:57No data—
Mon 26 OctUtrecht Centraal 19:280 min—
Thu 22 OctSchiphol Airport 19:08No data—
Wed 21 OctSchiphol Airport 19:10No data—
Tue 20 OctSchiphol Airport 19:15No data—
Mon 19 OctSchiphol Airport 19:290 min—
Thu 15 OctVeenendaal-De Klomp 19:300 min—
Wed 14 OctSchiedam Centrum 19:360 min—
Tue 13 OctSchiphol Airport 19:290 min—
Mon 12 OctSchiphol Airport 19:33Partial coverage0 min—
Thu 8 OctUtrecht Centraal 19:29+1 min—
Wed 7 OctUtrecht Centraal 19:33+2 min+4 min
Tue 6 OctUtrecht Centraal 19:29Partial coverage+1 min+1 min
Thu 1 OctUtrecht Centraal 18:15No data—
Wed 30 SeptUtrecht Centraal 18:15No data—
Tue 29 SeptUtrecht Centraal 18:15No data—
Mon 28 SeptUtrecht Centraal 18:15No data—
Thu 24 SeptVeenendaal-De Klomp 17:46No data—
Wed 23 SeptUtrecht Centraal 18:15No data—
Tue 22 SeptUtrecht Centraal 18:15No data—
Mon 21 SeptUtrecht Centraal 18:15No data—
Thu 17 SeptUtrecht Centraal 18:15No data—
Wed 16 SeptUtrecht Centraal 18:15No data—
Tue 15 SeptUtrecht Centraal 18:15No data—