Train NS 2855 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 15:59 0 min

  1. Rotterdam Centraal15:20
  2. Rotterdam Alexander15:28
  3. Gouda15:38
  4. Utrecht Centraal15:57

Next service: tomorrow 15:20 from Rotterdam Centraal · Fri 6 Nov

Next departure 15:20 tomorrow · Rotterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 6 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 48 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

  • Sat 10 Oct Max en route +5 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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:20on time on time
15:28≈ on time ≈ +1 min
15:38 / 15:39≈ on time ≈ +1 min
15:57on 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
Thu 5 NovGouda 15:59Partial coverage0 min—
Wed 4 NovGouda 15:59Partial coverage0 min—
Tue 3 NovGouda 15:59No data—
Mon 2 NovGouda 15:590 min—
Sun 1 NovGouda 15:590 min—
Sat 31 OctGouda 15:580 min—
Fri 30 OctGouda 15:58No data—
Thu 29 OctGouda 15:59Partial coverage0 min—
Wed 28 OctGouda 15:58No data—
Tue 27 OctGouda 15:58No data—
Mon 26 OctGouda 15:590 min—
Fri 16 OctGouda 15:540 min—
Thu 15 OctGouda 15:59Partial coverage0 min—
Wed 14 OctGouda 15:59No data—
Tue 13 OctGouda 16:00No data—
Mon 12 OctGouda 15:590 min—
Sun 11 OctGouda 15:59+1 min+3 min
Sat 10 OctGouda 16:00+4 min+5 min
Fri 9 OctGouda 15:590 min—
Thu 8 OctGouda 15:58Partial coverage0 min—
Wed 7 OctGouda 15:58Partial coverage0 min—
Tue 6 OctGouda 16:01Partial coverage+2 min+2 min
Mon 5 OctGouda 15:580 min—
Sun 4 OctGouda 15:53No data—
Sat 3 OctGouda 15:53No data—
Fri 2 OctGouda 15:53No data—
Thu 1 OctGouda 15:54No data—
Wed 30 SeptGouda 15:54No data—
Tue 29 SeptGouda 15:53No data—
Mon 28 SeptGouda 15:54No data—