Train NS 2856 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 17:03 → Rotterdam Centraal 17:40 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 17:03 from Utrecht Centraal · Thu 5 Nov

Next departure 17:03 today · Utrecht Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 6 full · 8 partial · 6 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 7 full · 9 partial · 48 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 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

  • Mon 5 Oct Max en route +5 min · last fix heading to Rotterdam Alexander +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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