Train NS 2833 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 10:29 0 min

  1. Rotterdam Centraal09:50
  2. Rotterdam Alexander09:58
  3. Gouda10:08
  4. Utrecht Centraal10:27

Next service: tomorrow 09:50 from Rotterdam Centraal · Fri 13 Nov

Next departure 09:50 tomorrow · Rotterdam Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 4 full · 10 partial · 5 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 7 full · 14 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: +1 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

  • Mon 9 Nov Max en route +5 min · last fix heading to Gouda +5 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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 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, 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 10
09:50on time on time
09:58≈ on time ≈ on time
10:08 / 10:09≈ on time ≈ on time
10: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 12 NovGouda 10:29Partial coverage0 min—
Wed 11 NovGouda 10:29Partial coverage+1 min+2 min
Tue 10 NovGouda 10:29Partial coverage0 min—
Mon 9 NovGouda 10:37Partial coverage+5 min+5 min
Fri 6 NovGouda 10:39No data—
Thu 5 NovGouda 10:28No data—
Wed 4 NovGouda 10:29Partial coverage0 min—
Tue 3 NovGouda 10:42No data—
Mon 2 NovGouda 10:29Partial coverage0 min—
Sun 1 NovGouda 10:520 min—
Sat 31 OctGouda 10:280 min—
Fri 30 OctGouda 10:280 min—
Thu 29 OctGouda 10:28Partial coverage0 min—
Wed 28 OctGouda 10:28Partial coverage0 min—
Tue 27 OctGouda 10:29Partial coverage0 min—
Mon 26 OctGouda 10:28Partial coverage0 min—
Fri 16 OctGouda 10:280 min—
Thu 15 OctGouda 10:28No data—
Wed 14 OctGouda 10:28No data—
Tue 13 OctGouda 10:47No data—
Mon 12 OctGouda 10:31Partial coverage0 min—
Sun 11 OctGouda 12:150 min—
Sat 10 OctGouda 10:30+1 min+1 min
Fri 9 OctGouda 10:290 min—
Thu 8 OctGouda 10:29Partial coverage+1 min—
Wed 7 OctGouda 10:29Partial coverage0 min—
Tue 6 OctGouda 10:28Partial coverage0 min—
Mon 5 OctGouda 10:23No data—
Sun 4 OctGouda 10:24No data—
Sat 3 OctGouda 10:23No data—