Train NS 2865 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 17:50 → Utrecht Centraal 18:27 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 11 November +2 min

Next service: today 17:50 from Rotterdam Centraal · Thu 12 Nov

Next departure 17:50 today · Rotterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 6 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 46 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: +2 min

Last 30 days

Arrival delay at Utrecht 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=2
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 stops).

Last 90 days, 20 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
17:50on time on time
17:58≈ on time ≈ on time
18:08 / 18:09≈ on time ≈ on time
18: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
Wed 11 NovGouda 18:29Partial coverage+2 min+2 min
Tue 10 NovGouda 18:29Partial coverage+1 min+1 min
Mon 9 NovGouda 18:29Partial coverage+1 min+1 min
Fri 6 NovGouda 18:290 min—
Thu 5 NovGouda 18:29Partial coverage0 min—
Wed 4 NovRotterdam Centraal 18:34Partial coverage0 min—
Tue 3 NovGouda 18:29No data—
Mon 2 NovGouda 18:29No data—
Sun 1 NovGouda 18:290 min—
Sat 31 OctGouda 18:30+2 min+2 min
Fri 30 OctGouda 18:28No data—
Thu 29 OctRotterdam Alexander 18:31No data—
Wed 28 OctGouda 18:39Partial coverage0 min—
Tue 27 OctRotterdam Alexander 18:29No data—
Mon 26 OctGouda 18:37Partial coverage0 min—
Fri 16 OctGouda 18:290 min—
Thu 15 OctGouda 18:28Partial coverage0 min—
Wed 14 OctGouda 18:35No data—
Tue 13 OctGouda 18:28No data—
Mon 12 OctGouda 18:29Partial coverage0 min—
Sun 11 OctGouda 18:280 min—
Sat 10 OctGouda 18:280 min—
Fri 9 OctGouda 18:280 min—
Thu 8 OctRotterdam Alexander 18:290 min—
Wed 7 OctGouda 18:29Partial coverage0 min—
Tue 6 OctRotterdam Alexander 18:28Partial coverage0 min—
Mon 5 OctGouda 18:290 min—
Sun 4 OctGouda 18:23No data—
Sat 3 OctGouda 18:28No data—
Fri 2 OctGouda 18:23No data—