Train NS 2839 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:20 from Rotterdam Centraal · Thu 5 Nov

Next departure 11:20 today · Rotterdam Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 3 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 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, 18 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
11:20on time on time
11:28≈ on time ≈ on time
11:38 / 11:39≈ on time ≈ on time
11:57on 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
Wed 4 NovGouda 11:59Partial coverage0 min—
Tue 3 NovGouda 11:58No data—
Mon 2 NovGouda 11:59Partial coverage0 min—
Sun 1 NovGouda 11:590 min—
Sat 31 OctGouda 11:580 min—
Fri 30 OctGouda 11:530 min—
Thu 29 OctGouda 11:53Partial coverage0 min—
Wed 28 OctGouda 11:58Partial coverage0 min—
Tue 27 OctGouda 11:59Partial coverage0 min—
Mon 26 OctGouda 11:59Partial coverage0 min—
Fri 16 OctGouda 11:580 min—
Thu 15 OctGouda 12:00No data—
Wed 14 OctGouda 11:58Partial coverage0 min—
Tue 13 OctGouda 11:58No data—
Mon 12 OctGouda 11:59Partial coverage0 min—
Sun 11 OctRotterdam Alexander 12:00+1 min—
Sat 10 OctGouda 11:59+1 min+1 min
Fri 9 OctGouda 11:590 min—
Thu 8 OctGouda 11:58Partial coverage0 min—
Wed 7 OctRotterdam Alexander 12:00Partial coverage0 min—
Tue 6 OctGouda 11:58Partial coverage0 min—
Mon 5 OctGouda 11:53No data—
Sun 4 OctGouda 11:53No data—
Sat 3 OctGouda 11:56No data—
Fri 2 OctGouda 11:54No data—
Thu 1 OctGouda 11:53No data—
Wed 30 SeptGouda 11:55No data—
Tue 29 SeptGouda 11:53No data—
Mon 28 SeptGouda 11:53No data—
Sun 27 SeptGouda 11:53No data—