Train NS 2066 Utrecht Centraal – Delft Campus

Utrecht Centraal 19:48 → Delft Campus 20:41 Daily 0 h 53 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 19:48 from Utrecht Centraal · Sun 8 Nov

Next departure 19:48 today · Utrecht Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 11 full · 1 partial · 7 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 26 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 Delft Campus, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 16 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:48on time on time
20:06 / 20:08≈ on time ≈ on time
20:17≈ on time ≈ +1 min
20:28 / 20:30≈ on time ≈ +1 min
20:38≈ on time ≈ +1 min
20:41on 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
Sat 7 NovDelft 20:52Partial coverage0 min—
Fri 6 Nov— 20:24+1 min—
Wed 4 Nov— 20:27+3 min+3 min
Mon 2 Nov— 20:29No data—
Sun 1 NovRotterdam Alexander 20:290 min—
Sat 31 OctRotterdam Alexander 20:310 min—
Fri 30 Oct— 20:26No data—
Thu 29 Oct— 20:260 min—
Wed 28 Oct— 20:260 min—
Tue 27 Oct— 20:29No data—
Mon 26 Oct— 20:26No data—
Sat 17 OctDelft 20:480 min—
Fri 16 Oct— 20:25No data—
Thu 15 Oct— 20:29No data—
Wed 14 OctUtrecht Centraal 20:26No data—
Tue 13 Oct— 20:310 min—
Mon 12 Oct— 20:270 min—
Sun 11 OctRotterdam Alexander 20:300 min—
Sat 10 OctRotterdam Alexander 20:310 min—
Fri 9 Oct— 20:260 min—
Thu 8 Oct— 20:530 min—
Tue 6 Oct— 20:28+1 min+1 min
Mon 5 Oct— 20:27+1 min+1 min
Sun 4 OctRotterdam Alexander 20:31No data—
Sat 3 OctRotterdam Alexander 20:31No data—
Sun 27 SeptRotterdam Alexander 20:31No data—
Sat 26 SeptRotterdam Alexander 20:43No data—
Sun 20 SeptRotterdam Alexander 20:31No data—
Sat 19 SeptRotterdam Alexander 20:31No data—
Sun 13 SeptRotterdam Alexander 20:30No data—