Train NS 2047 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 12 November +3 min

Next service: today 13:05 from Rotterdam Centraal · Fri 13 Nov

Next departure 13:05 today · Rotterdam Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 7 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 33 full · 5 partial · 40 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: +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

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 74% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
13:05on time on time
13:13≈ on time ≈ on time
13:23 / 13:24≈ on time ≈ on time
13: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
Thu 12 NovGouda 13:44Partial coverage+3 min+3 min
Wed 11 NovGouda 13:440 min—
Tue 10 NovGouda 13:44+2 min+3 min
Mon 9 NovGouda 13:430 min—
Sun 8 NovGouda 13:430 min—
Sat 7 NovGouda 13:430 min—
Fri 6 NovGouda 13:44No data—
Thu 5 NovGouda 13:38Partial coverage0 min—
Wed 4 NovGouda 13:430 min—
Tue 3 NovGouda 13:43No data—
Mon 2 NovGouda 13:44No data—
Sun 1 NovGouda 13:440 min—
Sat 31 OctGouda 13:380 min—
Fri 30 OctGouda 13:44Partial coverage0 min—
Thu 29 OctGouda 13:43No data—
Wed 28 OctGouda 13:430 min—
Tue 27 OctGouda 13:460 min—
Mon 26 OctGouda 13:430 min—
Sat 17 OctGouda 13:43No data—
Fri 16 OctGouda 13:43No data—
Thu 15 OctGouda 13:43No data—
Wed 14 OctGouda 13:44No data—
Tue 13 OctGouda 13:430 min—
Mon 12 OctGouda 13:440 min—
Sun 11 OctRotterdam Centraal 13:43No data—
Sat 10 OctGouda 13:430 min—
Fri 9 OctGouda 13:44Partial coverage0 min—
Thu 8 OctGouda 13:43Partial coverage0 min—
Wed 7 OctGouda 13:440 min—
Tue 6 OctGouda 13:430 min—