Train NS 2057 Delft Campus – Utrecht Centraal

Delft Campus 15:18 → Utrecht Centraal 16:12 Daily 0 h 54 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Delft Campus15:18
  2. Delft15:21
  3. Den Haag HS15:28
  4. Lansingerland-Zoetermeer15:41
  5. Gouda15:51
  6. Utrecht Centraal16:12

Next service: tomorrow 15:18 from Delft Campus · Sun 8 Nov

Next departure 15:18 tomorrow · Delft Campus
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 8 no data
On-time · 90 days
95%
56/59 runs under 3 min
RT coverage: 58 full · 1 partial · 20 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 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

  • Sun 16 Aug Max en route +24 min · last fix heading to Rotterdam Centraal +24 min
  • Mon 12 Oct Max en route +6 min · last fix heading to Gouda +6 min
  • Tue 15 Sept Max en route +3 min · last fix heading to Rotterdam Centraal +3 min

Distribution · 90 days

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

  • Early 34% · 20
  • On time 61% · 36
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • 89% T n=9
  • 100% W n=9
  • 100% T n=8
  • 100% F n=9
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 59 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
15:18on time on time
15:21≈ on time ≈ on time
15:28 / 15:30≈ on time ≈ on time
15:41≈ on time ≈ +1 min
15:51 / 15:54≈ on time ≈ +1 min
16:12on 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 16:14Partial coverage0 min+1 min
Fri 6 NovGouda 16:14No data—
Thu 5 NovGouda 16:140 min—
Wed 4 NovGouda 16:14+1 min—
Tue 3 NovGouda 16:08No data—
Mon 2 NovGouda 16:09No data—
Sun 1 NovGouda 16:090 min—
Sat 31 OctGouda 16:130 min—
Fri 30 OctGouda 16:150 min—
Thu 29 OctGouda 16:24No data—
Wed 28 OctGouda 16:130 min—
Tue 27 OctGouda 16:160 min—
Mon 26 OctGouda 16:150 min—
Sat 17 OctGouda 16:33No data—
Fri 16 OctRotterdam Centraal 16:130 min—
Thu 15 OctGouda 16:14No data—
Wed 14 OctGouda 16:14No data—
Tue 13 OctGouda 16:14No data—
Mon 12 OctGouda 16:26+6 min+6 min
Sun 11 OctGouda 16:130 min—
Sat 10 OctGouda 16:15+1 min+3 min
Fri 9 OctGouda 16:140 min—
Thu 8 OctGouda 16:130 min+1 min
Wed 7 OctGouda 16:16+1 min+1 min
Tue 6 OctGouda 16:16+2 min+3 min
Mon 5 OctGouda 16:15+1 min—
Sun 4 OctRotterdam Alexander 23:47−3 min+9 min
Sat 3 OctGouda 16:10No data—
Fri 2 OctRotterdam Alexander 16:11−3 min+2 min
Thu 1 OctRotterdam Centraal 19:51−3 min—