Train NS 2064 Utrecht Centraal – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

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

Next departure 19:18 today · Utrecht Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 15 full · 2 partial · 2 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 18 full · 2 partial · 26 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: +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

  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 min
  • Tue 6 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 50% T n=2
  • 67% W n=3
  • 100% T n=4
  • 100% F n=3
  • 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, 20 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
19:18on time on time
19:36 / 19:37≈ on time ≈ +1 min
19:46≈ on time ≈ +2 min
19:55on time +3 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:540 min—
Wed 4 Nov— 19:59+2 min+2 min
Sun 1 NovRotterdam Alexander 19:59Partial coverage0 min—
Sat 31 OctRotterdam Alexander 20:000 min—
Fri 30 Oct— 19:570 min—
Thu 29 Oct— 19:59+1 min+2 min
Wed 28 Oct— 19:560 min—
Tue 27 Oct— 20:030 min—
Mon 26 Oct— 20:030 min—
Sat 17 OctDelft 20:180 min—
Fri 16 Oct— 19:560 min—
Thu 15 Oct— 19:560 min—
Wed 14 OctRotterdam Alexander 20:00No data—
Tue 13 Oct— 19:57No data—
Mon 12 Oct— 20:020 min—
Sun 11 OctRotterdam Alexander 20:02Partial coverage+1 min—
Sat 10 OctRotterdam Alexander 20:010 min—
Fri 9 Oct— 20:130 min—
Thu 8 Oct— 19:560 min—
Wed 7 Oct— 19:56+3 min+3 min
Tue 6 Oct— 19:53+3 min+3 min
Mon 5 Oct— 20:00+2 min+2 min
Sun 4 OctRotterdam Alexander 20:01No data—
Sat 3 OctRotterdam Alexander 20:02No data—
Sun 27 SeptRotterdam Alexander 20:03No data—
Sat 26 SeptRotterdam Alexander 20:01No data—
Sun 20 SeptRotterdam Alexander 20:00No data—
Sat 19 SeptRotterdam Alexander 20:01No data—
Sun 13 SeptRotterdam Alexander 20:08No data—
Sat 12 SeptRotterdam Alexander 20:01No data—