Train NS 2834 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 11:33 → Rotterdam Centraal 12:10 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:33 from Utrecht Centraal · Thu 5 Nov

Next departure 11:33 today · Utrecht Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 8 full · 5 partial · 7 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 8 full · 6 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% 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, 14 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
11:33on time on time
11:51 / 11:52≈ on time ≈ on time
12:01≈ on time ≈ on time
12:10on time on time

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 4 NovRotterdam Alexander 12:14Partial coverage0 min—
Tue 3 NovRotterdam Alexander 12:17No data—
Mon 2 NovRotterdam Alexander 12:24Partial coverage0 min—
Sun 1 NovRotterdam Alexander 12:17+1 min—
Sat 31 OctRotterdam Alexander 12:160 min—
Fri 30 OctRotterdam Alexander 12:16No data—
Thu 29 OctRotterdam Alexander 12:170 min—
Wed 28 OctRotterdam Alexander 12:16Partial coverage0 min—
Tue 27 OctRotterdam Alexander 12:16No data—
Mon 26 OctRotterdam Alexander 12:16Partial coverage0 min—
Fri 16 OctRotterdam Alexander 12:170 min—
Thu 15 OctRotterdam Alexander 12:190 min—
Wed 14 OctRotterdam Alexander 12:16No data—
Tue 13 OctRotterdam Alexander 12:16No data—
Mon 12 OctRotterdam Alexander 12:16No data—
Sun 11 OctRotterdam Alexander 12:15No data—
Sat 10 OctRotterdam Alexander 12:160 min—
Fri 9 OctRotterdam Alexander 12:180 min—
Thu 8 OctRotterdam Alexander 12:160 min—
Wed 7 OctRotterdam Alexander 12:15Partial coverage0 min—
Tue 6 OctRotterdam Alexander 12:16Partial coverage0 min—
Mon 5 OctRotterdam Alexander 12:19No data—
Sun 4 OctRotterdam Alexander 12:20No data—
Sat 3 OctRotterdam Alexander 12:22No data—
Fri 2 OctRotterdam Alexander 12:16No data—
Thu 1 OctRotterdam Alexander 12:16No data—
Wed 30 SeptRotterdam Alexander 12:15No data—
Tue 29 SeptRotterdam Alexander 12:16No data—
Mon 28 SeptRotterdam Alexander 12:15No data—
Sun 27 SeptRotterdam Alexander 12:17No data—