Train NS 2068 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 20:18 → Rotterdam Centraal 20:55 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +16 min

Next service: today 20:18 from Utrecht Centraal · Thu 5 Nov

Next departure 20:18 today · Utrecht Centraal
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 7 full · 4 partial · 9 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 9 full · 4 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +17 min · last fix heading to — +16 min
  • Tue 6 Oct Max en route +9 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 8% · 1
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
20:18on time +2 min
20:36 / 20:37≈ on time ≈ +7 min
20:46≈ on time ≈ +8 min
20:55+1 min +10 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 Nov— 21:29+16 min+17 min
Tue 3 Nov— 21:05No data—
Mon 2 Nov— 20:54No data—
Sun 1 NovRotterdam Alexander 20:59Partial coverage0 min—
Sat 31 OctRotterdam Alexander 21:01Partial coverage0 min—
Thu 29 Oct— 20:570 min—
Wed 28 Oct— 21:030 min—
Tue 27 Oct— 20:57No data—
Mon 26 Oct— 20:59No data—
Sat 17 OctDelft 21:190 min—
Fri 16 Oct— 20:56No data—
Thu 15 Oct— 20:56No data—
Wed 14 Oct— 21:01No data—
Tue 13 Oct— 20:56No data—
Mon 12 Oct— 20:57No data—
Sun 11 OctRotterdam Alexander 21:00Partial coverage0 min—
Sat 10 OctRotterdam Alexander 21:00Partial coverage0 min—
Fri 9 Oct— 20:570 min—
Thu 8 Oct— 20:58+1 min+1 min
Wed 7 Oct— 21:00+2 min+2 min
Tue 6 Oct— 21:12+8 min+9 min
Mon 5 Oct— 20:58+1 min—
Sun 4 OctRotterdam Alexander 21:02No data—
Sat 3 OctRotterdam Alexander 21:01No data—
Sun 27 SeptRotterdam Alexander 21:02No data—
Sat 26 SeptRotterdam Alexander 21:01No data—
Sun 20 SeptRotterdam Alexander 21:01No data—
Sat 19 SeptRotterdam Alexander 21:01No data—
Sun 13 SeptRotterdam Alexander 21:01No data—
Sat 12 SeptRotterdam Alexander 21:01No data—