Train NS 2059 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 16:05 from Rotterdam Centraal · Fri 6 Nov

Next departure 16:05 today · Rotterdam Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 8 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 33 full · 15 partial · 30 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

Distribution · 90 days

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

  • Early 29% · 14
  • On time 71% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 48 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
16:05on time on time
16:13≈ on time ≈ on time
16:23 / 16:24≈ on time ≈ on time
16: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 5 NovGouda 16:39Partial coverage0 min—
Wed 4 NovGouda 16:44Partial coverage0 min—
Tue 3 NovGouda 16:43No data—
Mon 2 NovGouda 16:38No data—
Sun 1 NovGouda 16:45Partial coverage+1 min+2 min
Sat 31 OctGouda 16:43Partial coverage0 min—
Fri 30 OctGouda 16:44No data—
Thu 29 OctGouda 16:50No data—
Wed 28 OctGouda 16:42Partial coverage0 min—
Tue 27 OctGouda 16:44Partial coverage0 min—
Mon 26 OctGouda 16:45No data—
Sat 17 OctGouda 16:450 min—
Fri 16 OctRotterdam Centraal 16:42No data—
Thu 15 OctGouda 16:44No data—
Wed 14 OctGouda 16:44No data—
Tue 13 OctGouda 16:43Partial coverage0 min—
Mon 12 OctGouda 16:44Partial coverage0 min—
Sun 11 OctGouda 16:43Partial coverage0 min—
Sat 10 OctGouda 16:44Partial coverage+1 min+1 min
Fri 9 OctGouda 16:44Partial coverage+1 min+1 min
Thu 8 OctGouda 16:44Partial coverage0 min—
Wed 7 OctGouda 16:43Partial coverage0 min—
Tue 6 OctGouda 16:42Partial coverage0 min—
Mon 5 OctGouda 16:44Partial coverage+1 min+1 min
Sun 4 OctRotterdam Alexander 00:24−1 min+6 min
Sat 3 OctRotterdam Centraal 19:010 min+6 min
Fri 2 OctRotterdam Centraal 00:560 min—
Thu 1 OctRotterdam Centraal 00:560 min+1 min
Wed 30 SeptRotterdam Alexander 01:00−1 min+2 min
Tue 29 SeptRotterdam Centraal 18:190 min—