Train NS 2862 Utrecht Centraal – Rotterdam Centraal

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

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 18:33 from Utrecht Centraal · Mon 9 Nov

Next departure 18:33 Monday · Utrecht Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 4 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 13 full · 6 partial · 24 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: +1 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

  • Wed 28 Oct Max en route +8 min · last fix heading to — +8 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:33on time on time
18:51 / 18:52≈ on time ≈ +2 min
19:01≈ on time ≈ +3 min
19:10on time +4 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 NovUtrecht Centraal 19:13Partial coverage+1 min+1 min
Thu 5 Nov— 19:140 min—
Wed 4 Nov— 19:120 min—
Mon 2 NovUtrecht Centraal 19:140 min—
Sun 1 NovRotterdam Alexander 19:14Partial coverage0 min—
Sat 31 OctRotterdam Alexander 19:16Partial coverage0 min—
Fri 30 OctGouda 19:06No data—
Thu 29 Oct— 19:11+1 min—
Wed 28 Oct— 19:17+8 min+8 min
Tue 27 Oct— 19:140 min—
Mon 26 Oct— 18:410 min—
Fri 16 OctRotterdam Alexander 19:16No data—
Thu 15 Oct— 19:140 min—
Wed 14 OctRotterdam Alexander 19:16No data—
Tue 13 OctUtrecht Centraal 19:17No data—
Mon 12 OctUtrecht Centraal 19:110 min—
Sun 11 OctRotterdam Alexander 19:16Partial coverage0 min—
Sat 10 OctRotterdam Alexander 19:16Partial coverage0 min—
Fri 9 OctUtrecht Centraal 19:11Partial coverage0 min—
Thu 8 Oct— 19:120 min—
Wed 7 Oct— 19:14+2 min+2 min
Tue 6 Oct— 19:110 min—
Mon 5 Oct— 19:11+4 min+4 min
Sun 4 OctRotterdam Alexander 19:15No data—
Sat 3 OctRotterdam Alexander 19:19No data—
Fri 2 OctUtrecht Centraal 18:47No data—
Sun 27 SeptRotterdam Alexander 19:19No data—
Sat 26 SeptRotterdam Alexander 19:24No data—
Fri 25 SeptUtrecht Centraal 18:47No data—
Sun 20 SeptRotterdam Alexander 19:15No data—