Train NS 2052 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 16:59 No data

  1. Utrecht Centraal16:18
  2. Gouda16:36
  3. Rotterdam Alexander16:46
  4. Rotterdam Centraal16:55

Next service: tomorrow 16:18 from Utrecht Centraal · Wed 4 Nov

Full trip card
Next departure 16:18 tomorrow · Utrecht Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 9 no data
On-time · 90 days
88%
45/51 runs under 3 min
RT coverage: 41 full · 10 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Rotterdam 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 16 Aug Max en route +34 min · last fix heading to Rotterdam Alexander +33 min
  • Fri 14 Aug Max en route +31 min · last fix heading to Rotterdam Alexander +31 min
  • Fri 2 Oct Max en route +6 min · last fix heading to Rotterdam Alexander +6 min
  • Thu 17 Sept Max en route +4 min · last fix heading to Rotterdam Alexander +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Rotterdam Alexander +4 min

Distribution · 90 days

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

  • Early 33% · 17
  • On time 55% · 28
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 4% · 2

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 100% W n=5
  • 86% T n=7
  • 75% F n=8
  • 67% S n=6
  • 88% S n=8

Stops and timetable

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

StopSched.
Utrecht Centraal
16:18
Gouda
16:36 / 16:37
Rotterdam Alexander
16:46
Rotterdam Centraal
16:55

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.

Recent runs

DateLast stopFinalMax
Tue 3 NovRotterdam Alexander 16:59No data—
Mon 2 NovRotterdam Alexander 16:59No data—
Sun 1 NovRotterdam Alexander 17:01Partial coverage0 min—
Sat 31 OctRotterdam Alexander 17:01No data—
Fri 30 OctRotterdam Alexander 17:03Partial coverage0 min—
Thu 29 OctRotterdam Alexander 17:21No data—
Wed 28 OctRotterdam Alexander 17:02No data—
Tue 27 OctGouda 17:20Partial coverage0 min—
Mon 26 OctRotterdam Alexander 17:000 min—
Sat 17 OctDelft 17:36No data—
Fri 16 OctUtrecht Centraal 16:56Partial coverage0 min—
Thu 15 OctRotterdam Alexander 17:01No data—
Wed 14 OctRotterdam Alexander 17:01No data—
Tue 13 OctRotterdam Alexander 17:02No data—
Mon 12 OctRotterdam Alexander 17:03+2 min+4 min
Sun 11 OctRotterdam Alexander 17:01Partial coverage0 min—
Sat 10 OctRotterdam Alexander 17:05Partial coverage+4 min+4 min
Fri 9 OctRotterdam Alexander 17:01Partial coverage+1 min—
Thu 8 OctRotterdam Alexander 17:00Partial coverage0 min—
Wed 7 OctRotterdam Alexander 17:01Partial coverage0 min—
Tue 6 OctRotterdam Alexander 17:01Partial coverage0 min—
Mon 5 OctRotterdam Alexander 17:00+2 min+2 min
Sun 4 OctRotterdam Alexander 17:01No data—
Sat 3 OctRotterdam Alexander 23:20−2 min+4 min
Fri 2 OctRotterdam Alexander 23:27+6 min+6 min
Thu 1 OctRotterdam Alexander 18:53−2 min—
Wed 30 SeptRotterdam Alexander 18:35−7 min—
Tue 29 SeptRotterdam Alexander 17:200 min—
Mon 28 SeptRotterdam Alexander 17:05No data—
Sun 27 SeptRotterdam Alexander 17:01No data—