Train NS 2843 Rotterdam Centraal – Utrecht Centraal

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 12:20 from Rotterdam Centraal · Mon 9 Nov

Next departure 12:20 Monday · Rotterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 9 full · 3 partial · 8 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 12 full · 4 partial · 48 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=1
  • 100% W n=3
  • 100% T n=4
  • 100% F n=2
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 16 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
12:20on time on time
12:28≈ on time ≈ on time
12:38 / 12:39≈ on time ≈ on time
12:57on time on time

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 NovGouda 12:58No data—
Thu 5 NovGouda 12:58Partial coverage0 min—
Wed 4 NovGouda 12:590 min—
Tue 3 NovGouda 12:59No data—
Mon 2 NovGouda 12:580 min—
Sun 1 NovGouda 12:590 min—
Sat 31 OctGouda 12:58+1 min+1 min
Fri 30 OctGouda 12:58No data—
Thu 29 OctGouda 12:59Partial coverage0 min—
Wed 28 OctGouda 12:580 min—
Tue 27 OctGouda 13:01No data—
Mon 26 OctGouda 13:200 min—
Fri 16 OctGouda 13:230 min—
Thu 15 OctGouda 13:10Partial coverage0 min—
Wed 14 OctGouda 13:00No data—
Tue 13 OctGouda 12:58No data—
Mon 12 OctGouda 12:59No data—
Sun 11 OctGouda 12:58No data—
Sat 10 OctGouda 12:590 min—
Fri 9 OctGouda 12:590 min—
Thu 8 OctGouda 12:58Partial coverage0 min—
Wed 7 OctGouda 15:300 min—
Tue 6 OctGouda 12:580 min—
Mon 5 OctGouda 12:580 min—
Sun 4 OctGouda 12:53No data—
Sat 3 OctGouda 12:57No data—
Fri 2 OctGouda 12:54No data—
Thu 1 OctGouda 12:53No data—
Wed 30 SeptGouda 12:53No data—
Tue 29 SeptGouda 12:53No data—