Train NS 2046 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 14:48 → Rotterdam Centraal 15:25 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 14:48 from Utrecht Centraal · Fri 13 Nov

Next departure 14:48 today · Utrecht Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 6 no data
On-time · 90 days
95%
62/65 runs under 3 min
RT coverage: 60 full · 5 partial · 13 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

  • Sat 10 Oct Max en route +6 min · last fix heading to Rotterdam Alexander +6 min
  • Thu 20 Aug Max en route +4 min · last fix heading to Rotterdam Alexander +3 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Rotterdam Alexander +3 min

Distribution · 90 days

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

  • Early 15% · 10
  • On time 80% · 52
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=9
  • 100% W n=8
  • 92% T n=12
  • 100% F n=9
  • 89% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 65 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
14:48on time on time
15:06 / 15:07≈ on time ≈ +1 min
15:16≈ on time ≈ +1 min
15:25on 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 NovUtrecht Centraal 15:30Partial coverage0 min—
Wed 11 NovRotterdam Alexander 15:290 min—
Tue 10 NovRotterdam Alexander 15:290 min—
Mon 9 NovRotterdam Alexander 15:29+3 min+3 min
Sun 8 NovDelft 15:490 min—
Sat 7 NovDelft 15:53+1 min+3 min
Fri 6 NovRotterdam Alexander 15:29No data—
Thu 5 NovRotterdam Alexander 15:29Partial coverage0 min—
Wed 4 NovRotterdam Alexander 15:29No data—
Tue 3 NovRotterdam Alexander 15:29No data—
Mon 2 NovRotterdam Alexander 15:29No data—
Sun 1 NovRotterdam Alexander 15:32No data—
Sat 31 OctRotterdam Alexander 15:31No data—
Fri 30 OctRotterdam Alexander 15:310 min—
Thu 29 OctRotterdam Alexander 15:31Partial coverage0 min—
Wed 28 OctRotterdam Alexander 15:310 min—
Tue 27 OctRotterdam Alexander 15:320 min—
Mon 26 OctRotterdam Alexander 15:310 min—
Sat 17 OctDelft 15:490 min—
Fri 16 OctRotterdam Alexander 15:330 min—
Thu 15 OctRotterdam Alexander 15:31Partial coverage0 min—
Wed 14 OctRotterdam Alexander 15:31No data—
Tue 13 OctRotterdam Alexander 15:31No data—
Mon 12 OctRotterdam Alexander 15:320 min—
Sun 11 OctRotterdam Alexander 15:34+2 min+4 min
Sat 10 OctRotterdam Alexander 15:33+6 min+6 min
Fri 9 OctRotterdam Alexander 15:310 min—
Thu 8 OctRotterdam Alexander 15:31Partial coverage0 min—
Wed 7 OctRotterdam Alexander 15:310 min—
Tue 6 OctRotterdam Alexander 15:310 min—