Train NS 2867 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 11 November +3 min

Next service: today 18:20 from Rotterdam Centraal · Thu 12 Nov

Next departure 18:20 today · Rotterdam Centraal
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 3 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 26 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 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 100% F n=3
  • 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, 22 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:20on time on time
18:28≈ on time ≈ +1 min
18:38 / 18:39≈ on time ≈ +1 min
18:57on 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
Wed 11 Nov— 18:59+3 min+3 min
Tue 10 NovRotterdam Centraal 18:590 min+1 min
Mon 9 Nov— 18:590 min—
Fri 6 NovGouda 18:580 min—
Thu 5 Nov— 19:130 min—
Wed 4 Nov— 18:590 min—
Tue 3 Nov— 18:580 min—
Mon 2 NovRotterdam Alexander 19:04+3 min+3 min
Sun 1 NovGouda 18:59+1 min—
Sat 31 OctGouda 19:000 min+1 min
Fri 30 OctGouda 19:32No data—
Thu 29 Oct— 18:590 min—
Wed 28 Oct— 18:580 min—
Tue 27 Oct— 18:590 min—
Mon 26 Oct— 19:01No data—
Fri 16 OctGouda 18:580 min—
Thu 15 OctRotterdam Alexander 19:010 min—
Wed 14 OctGouda 18:58No data—
Tue 13 OctGouda 18:58No data—
Mon 12 OctGouda 18:590 min—
Sun 11 OctGouda 18:530 min—
Sat 10 OctGouda 18:580 min—
Fri 9 OctRotterdam Alexander 18:580 min—
Thu 8 Oct— 18:590 min—
Wed 7 Oct— 19:00No data—
Tue 6 Oct— 19:00+3 min+3 min
Mon 5 Oct— 19:03+4 min+4 min
Sun 4 OctGouda 18:53No data—
Sat 3 OctGouda 18:54No data—
Fri 2 OctGouda 18:53No data—