Train NS 2885 Rotterdam Centraal – Utrecht Centraal

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

Running now · updated 00:28

Heading to Utrecht Centraal No data

Estimated arrival at Utrecht Centraal 23:27 · 0 km/h

  1. Rotterdam Centraal22:50
  2. Rotterdam Alexander22:58
  3. Gouda23:08
  4. Utrecht Centraal23:27
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 1 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 10 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: 0 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

Worst days

  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 6 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 75% W n=4
  • 100% T n=2
  • 100% F n=4
  • 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, 21 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
22:50on time on time
22:58≈ on time ≈ on time
23:08 / 23:09≈ on time ≈ on time
23: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
Fri 6 Nov— 00:240 min—
Thu 5 Nov— 01:140 min—
Wed 4 Nov— 23:290 min—
Mon 2 Nov— 23:290 min—
Sun 1 NovRotterdam Centraal 23:290 min—
Sat 31 OctGouda 01:150 min—
Fri 30 Oct— 01:190 min—
Wed 28 Oct— 23:320 min—
Tue 27 Oct— 23:350 min—
Mon 26 Oct— 23:280 min—
Fri 16 Oct— 23:50+1 min—
Thu 15 Oct— 23:54No data—
Wed 14 Oct— 23:500 min—
Tue 13 Oct— 23:530 min—
Mon 12 Oct— 23:53+1 min—
Sun 11 OctGouda 23:280 min—
Sat 10 Oct— 01:200 min—
Fri 9 Oct— 23:340 min—
Thu 8 Oct— 23:350 min—
Wed 7 Oct— 23:36+4 min+4 min
Tue 6 Oct— 01:17+3 min+3 min
Mon 5 Oct— 23:31+1 min—
Sun 4 OctGouda 23:23No data—
Sat 3 OctGouda 23:24No data—
Sun 27 SeptGouda 23:23No data—
Sat 26 SeptGouda 23:22No data—
Sun 20 SeptGouda 23:24No data—
Sat 19 SeptRotterdam Alexander 23:08No data—
Sun 6 SeptGouda 23:22No data—
Sat 5 SeptRotterdam Alexander 23:11No data—