Train NS 2069 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 18:35 → Utrecht Centraal 19:12 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 19:14 +2 min

  1. Rotterdam Centraal18:35
  2. Rotterdam Alexander18:43
  3. Gouda18:53
  4. Utrecht Centraal19:12

Next service: tomorrow 18:35 from Rotterdam Centraal · Sat 7 Nov

Next departure 18:35 tomorrow · Rotterdam Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 13 full · 7 partial · 0 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 16 full · 7 partial · 34 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

  • Sun 1 Nov Max en route +6 min · last fix heading to Gouda +5 min
  • Wed 7 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
18:35on time +3 min
18:43≈ on time ≈ +4 min
18:53 / 18:54≈ on time ≈ +4 min
19:12on time +3 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
Fri 6 NovRotterdam Alexander 19:14Partial coverage+2 min+2 min
Thu 5 Nov— 19:140 min—
Wed 4 Nov— 19:130 min—
Sun 1 NovGouda 19:13+5 min+6 min
Sat 31 OctGouda 19:13Partial coverage0 min—
Fri 30 OctGouda 19:20Partial coverage0 min—
Thu 29 Oct— 19:18+2 min+5 min
Wed 28 Oct— 19:130 min—
Tue 27 Oct— 19:140 min—
Mon 26 Oct— 19:150 min—
Sat 17 OctGouda 19:140 min—
Fri 16 Oct— 19:130 min—
Thu 15 Oct— 19:130 min—
Wed 14 OctGouda 19:13Partial coverage0 min—
Tue 13 OctRotterdam Centraal 19:130 min—
Mon 12 OctRotterdam Alexander 19:27Partial coverage0 min—
Sun 11 OctGouda 19:130 min—
Sat 10 OctGouda 19:15Partial coverage+1 min+2 min
Fri 9 OctRotterdam Centraal 19:13Partial coverage0 min—
Thu 8 Oct— 19:140 min—
Wed 7 Oct— 19:20+4 min+5 min
Tue 6 Oct— 19:14+2 min+2 min
Mon 5 Oct— 19:15+1 min+1 min
Sun 4 OctGouda 19:08No data—
Sat 3 OctGouda 19:10No data—
Fri 2 OctRotterdam Alexander 18:57No data—
Sun 27 SeptGouda 19:08No data—
Sat 26 SeptGouda 19:08No data—
Fri 25 SeptRotterdam Centraal 18:49No data—
Sun 20 SeptGouda 19:09No data—