Train NS 2828 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 10:03 → Rotterdam Centraal 10:40 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 10:03 from Utrecht Centraal · Fri 6 Nov

Next departure 10:03 today · Utrecht Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 7 full · 6 partial · 7 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 9 full · 6 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Sat 31 Oct Max en route +8 min · last fix heading to Rotterdam Alexander +8 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Rotterdam Alexander +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 67% W n=3
  • 100% T n=4
  • 100% F n=2
  • 50% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 15 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
10:03on time on time
10:21 / 10:22≈ on time ≈ +5 min
10:31≈ on time ≈ +7 min
10:40on time +8 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 NovRotterdam Alexander 10:44Partial coverage0 min—
Wed 4 NovRotterdam Alexander 10:440 min—
Tue 3 NovRotterdam Alexander 10:59No data—
Mon 2 NovRotterdam Alexander 10:47Partial coverage0 min—
Sun 1 NovRotterdam Alexander 10:47No data—
Sat 31 OctRotterdam Alexander 10:54+8 min+8 min
Fri 30 OctRotterdam Alexander 10:46No data—
Thu 29 OctRotterdam Alexander 10:48Partial coverage0 min—
Wed 28 OctRotterdam Alexander 10:500 min—
Tue 27 OctRotterdam Alexander 10:46No data—
Mon 26 OctRotterdam Alexander 10:47Partial coverage0 min—
Fri 16 OctRotterdam Alexander 10:470 min—
Thu 15 OctRotterdam Alexander 10:46Partial coverage0 min—
Wed 14 OctRotterdam Alexander 10:49No data—
Tue 13 OctRotterdam Alexander 10:46No data—
Mon 12 OctRotterdam Alexander 10:45No data—
Sun 11 OctRotterdam Alexander 10:460 min—
Sat 10 OctRotterdam Alexander 10:47+1 min+2 min
Fri 9 OctRotterdam Alexander 10:460 min—
Thu 8 OctRotterdam Alexander 10:46Partial coverage0 min—
Wed 7 OctRotterdam Alexander 11:02+7 min+7 min
Tue 6 OctRotterdam Alexander 10:47+2 min+2 min
Mon 5 OctRotterdam Alexander 10:51No data—
Sun 4 OctRotterdam Alexander 10:48No data—
Sat 3 OctRotterdam Alexander 10:46No data—
Fri 2 OctRotterdam Alexander 10:46No data—
Thu 1 OctRotterdam Alexander 10:46No data—
Wed 30 SeptRotterdam Alexander 10:47No data—
Tue 29 SeptRotterdam Alexander 10:46No data—
Mon 28 SeptRotterdam Alexander 10:45No data—