Train NS 2038 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 12:48 → Rotterdam Centraal 13:25 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 12:48 from Utrecht Centraal · Thu 5 Nov

Next departure 12:48 today · Utrecht Centraal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 1 full · 12 partial · 8 no data
On-time · 90 days
96%
46/48 runs under 3 min
RT coverage: 34 full · 14 partial · 30 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: +3 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 +10 min · last fix heading to Rotterdam Alexander +9 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Rotterdam Alexander +3 min

Distribution · 90 days

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

  • Early 38% · 18
  • On time 58% · 28
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=9
  • 100% W n=7
  • 100% T n=6
  • 100% F n=6
  • 75% S n=8
  • 100% S n=5

Stops and timetable

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

Last 90 days, 48 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:48on time on time
13:06 / 13:07≈ 1 min early ≈ on time
13:16≈ 1 min early ≈ on time
13:251 min early 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 13:29Partial coverage0 min—
Tue 3 NovRotterdam Alexander 13:29Partial coverage0 min—
Mon 2 NovRotterdam Alexander 13:29No data—
Sun 1 NovRotterdam Alexander 13:32Partial coverage0 min—
Sat 31 OctRotterdam Alexander 13:40Partial coverage+9 min+10 min
Fri 30 OctRotterdam Alexander 13:31No data—
Thu 29 OctRotterdam Alexander 13:36No data—
Wed 28 OctRotterdam Alexander 13:31Partial coverage0 min—
Tue 27 OctRotterdam Alexander 13:31Partial coverage0 min—
Mon 26 OctRotterdam Alexander 13:44Partial coverage0 min—
Sat 17 OctDelft 13:480 min—
Fri 16 OctRotterdam Alexander 13:31No data—
Thu 15 OctRotterdam Alexander 13:31No data—
Wed 14 OctRotterdam Alexander 13:37No data—
Tue 13 OctRotterdam Alexander 13:31Partial coverage0 min—
Mon 12 OctRotterdam Alexander 13:31No data—
Sun 11 OctRotterdam Alexander 13:30Partial coverageNo data—
Sat 10 OctRotterdam Alexander 13:32Partial coverage+3 min+3 min
Fri 9 OctRotterdam Alexander 13:31Partial coverage0 min—
Thu 8 OctRotterdam Alexander 13:31Partial coverage0 min—
Wed 7 OctRotterdam Alexander 13:31Partial coverage0 min—
Tue 6 OctRotterdam Alexander 13:32Partial coverage0 min—
Mon 5 OctRotterdam Alexander 13:31Partial coverage0 min+2 min
Sun 4 OctRotterdam Alexander 23:09−1 min+3 min
Sat 3 OctRotterdam Alexander 18:50−1 min+2 min
Fri 2 OctRotterdam Alexander 00:130 min+8 min
Thu 1 OctRotterdam Alexander 13:31−2 min—
Wed 30 SeptRotterdam Alexander 00:170 min+2 min
Tue 29 SeptRotterdam Alexander 18:54−2 min+9 min
Mon 28 SeptRotterdam Alexander 18:35−4 min+3 min