Train NS 2055 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 15:05 → Utrecht Centraal 15:42 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

Running now · updated 15:29

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 15:42 · 129 km/h

  1. Rotterdam Centraal15:05
  2. Rotterdam Alexander15:13
  3. Gouda15:23
  4. Utrecht Centraal15:42

Today it is running worse than usual: typical arrival delay is 0 min; 84% of the last 19 runs arrived on time.

On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 12 full · 7 partial · 5 no data
On-time · 90 days
84%
46/55 runs under 3 min
RT coverage: 44 full · 11 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 23 Sept Max en route +31 min · last fix heading to Rotterdam Centraal +31 min
  • Sun 30 Aug Max en route +30 min · last fix heading to Rotterdam Centraal +29 min
  • Fri 21 Aug Max en route +11 min · last fix heading to Rotterdam Centraal +11 min
  • Tue 17 Nov Max en route +8 min · last fix heading to Gouda +7 min
  • Tue 1 Sept Max en route +6 min · last fix heading to Rotterdam Centraal +5 min

Distribution · 90 days

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

  • Early 24% · 13
  • On time 60% · 33
  • 3–10 min 11% · 6
  • 10–30 min 4% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=11
  • 70% T n=10
  • 78% W n=9
  • 100% T n=5
  • 83% F n=6
  • 86% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 55 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 10Today
15:05on time on time
15:13≈ on time ≈ +2 min
15:23 / 15:24≈ on time ≈ +3 min
15:42on time +5 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
Wed 18 NovGouda 15:24Partial coverage0 min—
Tue 17 NovGouda 15:52Partial coverage+7 min+8 min
Mon 16 NovGouda 15:440 min—
Sun 15 NovGouda 15:44+3 min+4 min
Sat 14 NovGouda 15:380 min—
Fri 13 NovGouda 15:430 min—
Thu 12 NovGouda 15:44Partial coverageNo data—
Wed 11 NovGouda 15:44Partial coverage+1 min+1 min
Tue 10 NovGouda 15:44Partial coverage+3 min+3 min
Mon 9 NovGouda 15:45+1 min+1 min
Sun 8 NovGouda 15:430 min—
Sat 7 NovGouda 15:440 min—
Fri 6 NovGouda 15:43No data—
Thu 5 NovGouda 15:44Partial coverage0 min—
Wed 4 NovGouda 15:44Partial coverage+2 min+2 min
Tue 3 NovGouda 15:43No data—
Mon 2 NovGouda 15:440 min—
Sun 1 NovGouda 15:41+1 min+8 min
Sat 31 OctGouda 15:430 min—
Fri 30 OctGouda 15:43No data—
Thu 29 OctGouda 15:44No data—
Wed 28 OctGouda 15:43Partial coverage0 min—
Tue 27 OctGouda 15:460 min—
Mon 26 OctGouda 15:450 min—
Sat 17 OctGouda 15:430 min—
Fri 16 OctRotterdam Centraal 15:43No data—
Thu 15 OctGouda 15:44No data—
Wed 14 OctGouda 15:43No data—
Tue 13 OctGouda 15:44Partial coverage0 min—
Mon 12 OctGouda 15:440 min—