Train NS 2051 Delft Campus – Utrecht Centraal

Delft Campus 13:48 → Utrecht Centraal 14:42 Daily 0 h 54 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 14:43 0 min

  1. Delft Campus13:48
  2. Delft13:51
  3. Den Haag HS13:58
  4. Lansingerland-Zoetermeer14:11
  5. Gouda14:21
  6. Utrecht Centraal14:42

Next service: tomorrow 13:48 from Delft Campus · Mon 9 Nov

Next departure 13:48 tomorrow · Delft Campus
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 14 full · 2 partial · 6 no data
On-time · 90 days
89%
59/66 runs under 3 min
RT coverage: 64 full · 2 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Utrecht 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

  • Fri 4 Sept Max en route +35 min · last fix heading to Gouda +35 min
  • Tue 25 Aug Max en route +17 min · last fix heading to Rotterdam Centraal +17 min
  • Mon 24 Aug Max en route +12 min · last fix heading to Rotterdam Centraal +12 min
  • Wed 16 Sept Max en route +11 min · last fix heading to Rotterdam Centraal +11 min
  • Sun 11 Oct Max en route +8 min · last fix heading to Gouda +7 min

Distribution · 90 days

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

  • Early 27% · 18
  • On time 62% · 41
  • 3–10 min 5% · 3
  • 10–30 min 5% · 3
  • 30+ min 2% · 1

On-time by weekday

  • 89% M n=9
  • 89% T n=9
  • 70% W n=10
  • 100% T n=12
  • 90% F n=10
  • 100% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 66 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
13:48on time on time
13:51≈ on time ≈ on time
13:58 / 14:00≈ on time ≈ +1 min
14:11≈ on time ≈ +2 min
14:21 / 14:24≈ on time ≈ +2 min
14:42on time +4 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
Sun 8 NovGouda 14:43Partial coverage0 min—
Sat 7 NovGouda 14:44Partial coverage0 min—
Fri 6 NovGouda 14:43No data—
Thu 5 NovGouda 14:430 min—
Wed 4 NovGouda 14:44+5 min+5 min
Tue 3 NovGouda 14:39No data—
Mon 2 NovGouda 14:38No data—
Sun 1 NovGouda 14:390 min—
Sat 31 OctGouda 14:430 min—
Fri 30 OctGouda 14:430 min—
Thu 29 OctGouda 14:450 min—
Wed 28 OctGouda 14:430 min—
Tue 27 OctGouda 14:380 min—
Mon 26 OctGouda 14:380 min—
Sat 17 OctGouda 14:38No data—
Fri 16 OctGouda 14:430 min—
Thu 15 OctGouda 14:440 min—
Wed 14 OctGouda 14:44No data—
Tue 13 OctGouda 14:43No data—
Mon 12 OctGouda 14:440 min—
Sun 11 OctGouda 14:52+7 min+8 min
Sat 10 OctGouda 14:430 min—
Fri 9 OctGouda 14:440 min—
Thu 8 OctGouda 14:430 min—
Wed 7 OctGouda 14:430 min—
Tue 6 OctGouda 14:44+1 min+1 min
Mon 5 OctGouda 14:450 min—
Sun 4 OctRotterdam Centraal 19:530 min+4 min
Sat 3 OctRotterdam Centraal 00:270 min+4 min
Fri 2 OctRotterdam Centraal 00:260 min+2 min