Train NS 2836 Utrecht Centraal – Rotterdam Centraal

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 12:03 from Utrecht Centraal · Mon 9 Nov

Next departure 12:03 tomorrow · Utrecht Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 8 full · 6 partial · 5 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 11 full · 8 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 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, 19 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
12:03on time on time
12:21 / 12:22≈ on time ≈ +1 min
12:31≈ on time ≈ +2 min
12:40on time +2 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 NovRotterdam Alexander 12:47No data—
Thu 5 NovRotterdam Alexander 12:48Partial coverage0 min—
Wed 4 NovRotterdam Alexander 12:440 min—
Tue 3 NovRotterdam Alexander 12:53No data—
Mon 2 NovRotterdam Alexander 12:44Partial coverage0 min—
Sun 1 NovRotterdam Alexander 12:470 min—
Sat 31 OctRotterdam Alexander 12:50+5 min+5 min
Fri 30 OctRotterdam Alexander 12:460 min—
Thu 29 OctRotterdam Alexander 12:46Partial coverage0 min—
Wed 28 OctRotterdam Alexander 12:460 min—
Tue 27 OctRotterdam Alexander 12:46No data—
Mon 26 OctRotterdam Alexander 12:46Partial coverage0 min—
Fri 16 OctRotterdam Alexander 12:460 min—
Thu 15 OctRotterdam Alexander 12:46Partial coverage0 min—
Wed 14 OctRotterdam Alexander 12:460 min—
Tue 13 OctRotterdam Alexander 12:46No data—
Mon 12 OctRotterdam Alexander 12:46Partial coverage0 min—
Sun 11 OctRotterdam Alexander 12:45No data—
Sat 10 OctRotterdam Alexander 12:47+1 min+2 min
Fri 9 OctRotterdam Alexander 12:460 min—
Thu 8 OctRotterdam Alexander 12:46Partial coverage0 min+1 min
Wed 7 OctRotterdam Alexander 12:450 min—
Tue 6 OctRotterdam Alexander 12:46Partial coverage+2 min+2 min
Mon 5 OctRotterdam Alexander 12:46+2 min+2 min
Sun 4 OctRotterdam Alexander 12:46No data—
Sat 3 OctRotterdam Alexander 12:46No data—
Fri 2 OctRotterdam Alexander 12:46No data—
Thu 1 OctRotterdam Alexander 12:46No data—
Wed 30 SeptRotterdam Alexander 12:46No data—
Tue 29 SeptRotterdam Alexander 12:46No data—