Train NS 2062 Utrecht Centraal – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 18:48 from Utrecht Centraal · Fri 6 Nov

Next departure 18:48 today · Utrecht Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 6 full · 3 partial · 12 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 8 full · 3 partial · 45 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • — W n=0
  • 100% T n=2
  • 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, 11 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
18:48on time on time
19:06 / 19:07≈ on time ≈ on time
19:16≈ on time ≈ +1 min
19: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 5 Nov— 19:24No data—
Wed 4 Nov— 19:27No data—
Tue 3 Nov— 19:390 min—
Mon 2 Nov— 19:290 min—
Sun 1 NovRotterdam Alexander 19:29Partial coverage0 min—
Sat 31 OctRotterdam Alexander 19:31No data—
Fri 30 OctUtrecht Centraal 19:26No data—
Thu 29 Oct— 19:260 min—
Wed 28 Oct— 19:26No data—
Tue 27 Oct— 19:27No data—
Mon 26 Oct— 19:30No data—
Sat 17 OctDelft 19:49No data—
Fri 16 Oct— 19:26No data—
Thu 15 Oct— 19:32No data—
Wed 14 OctRotterdam Alexander 19:30No data—
Tue 13 Oct— 19:27No data—
Mon 12 Oct— 19:260 min—
Sun 11 OctRotterdam Alexander 19:31Partial coverage0 min—
Sat 10 OctRotterdam Alexander 19:31Partial coverage+1 min+1 min
Fri 9 Oct— 19:270 min—
Thu 8 Oct— 19:270 min—
Tue 6 Oct— 19:210 min—
Mon 5 Oct— 19:31+2 min+2 min
Sun 4 OctRotterdam Alexander 19:32No data—
Sat 3 OctRotterdam Alexander 19:31No data—
Fri 2 OctUtrecht Centraal 19:02No data—
Sun 27 SeptRotterdam Alexander 19:31No data—
Sat 26 SeptRotterdam Alexander 19:30No data—
Sun 20 SeptRotterdam Alexander 19:31No data—
Sat 19 SeptRotterdam Alexander 19:31No data—