Train NS 2043 Rotterdam Centraal – Utrecht Centraal

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

Running now · updated 12:40

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 12:42 · 80 km/h

  1. Rotterdam Centraal12:05
  2. Rotterdam Alexander12:13
  3. Gouda12:23
  4. Utrecht Centraal12:42

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

On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 4 full · 8 partial · 10 no data
On-time · 90 days
95%
39/41 runs under 3 min
RT coverage: 28 full · 13 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

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

  • Early 24% · 10
  • On time 71% · 29
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=7
  • 100% T n=5
  • 80% F n=5
  • 80% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 41 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
12:05on time on time
12:13≈ on time ≈ on time
12:23 / 12:24≈ on time ≈ on time
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
Tue 10 NovGouda 12:39Partial coverage0 min—
Mon 9 NovGouda 12:43Partial coverage0 min+1 min
Sun 8 NovGouda 12:43+2 min+2 min
Sat 7 NovGouda 12:430 min—
Fri 6 NovGouda 12:44No data—
Thu 5 NovGouda 12:43No data—
Wed 4 NovGouda 12:44Partial coverage0 min—
Tue 3 NovGouda 12:43No data—
Mon 2 NovGouda 12:38No data—
Sun 1 NovGouda 12:390 min—
Sat 31 OctGouda 12:52Partial coverage+11 min+11 min
Fri 30 OctGouda 12:44No data—
Thu 29 OctGouda 12:56No data—
Wed 28 OctGouda 12:43Partial coverage0 min—
Tue 27 OctGouda 12:44Partial coverage0 min—
Mon 26 OctGouda 12:54Partial coverage0 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:43Partial coverage0 min—
Mon 12 OctGouda 12:44No data—
Sun 11 OctGouda 12:38Partial coverageNo data—
Sat 10 OctGouda 12:43Partial coverage0 min—
Fri 9 OctGouda 12:44Partial coverage0 min—
Thu 8 OctGouda 12:38No data—
Wed 7 OctGouda 12:43Partial coverage0 min—
Tue 6 OctGouda 12:44Partial coverage+2 min+2 min
Mon 5 OctGouda 12:44Partial coverage+1 min+1 min
Sun 4 OctGouda 12:39No data—