Train NS 2043 Delft Campus – Utrecht Centraal

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

✓ Today’s run finished

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

  1. Delft Campus11:48
  2. Delft11:51
  3. Den Haag HS11:58
  4. Lansingerland-Zoetermeer12:11
  5. Gouda12:21
  6. Utrecht Centraal12:42

Next service: tomorrow 11:48 from Delft Campus · Sun 8 Nov

Next departure 11:48 tomorrow · Delft Campus
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 11 no data
On-time · 90 days
95%
36/38 runs under 3 min
RT coverage: 37 full · 1 partial · 41 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: 0 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

  • Sat 31 Oct Max en route +11 min · last fix heading to Gouda +11 min
  • Fri 18 Sept Max en route +21 min · last fix heading to Rotterdam Alexander +6 min

Distribution · 90 days

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

  • Early 26% · 10
  • On time 68% · 26
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=5
  • 80% F n=5
  • 80% S n=5
  • 100% S n=3

Stops and timetable

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

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