Train NS 2845 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 12:50 → Utrecht Centraal 13:27 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 12:50 from Rotterdam Centraal · Thu 5 Nov

Next departure 12:50 today · Rotterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 13 full · 4 partial · 3 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Thu 8 Oct Max en route +3 min · last fix heading to Rotterdam Centraal +3 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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 67% T n=3
  • 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, 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
12:50on time on time
12:58≈ on time ≈ on time
13:08 / 13:09≈ on time ≈ +1 min
13:27on time +2 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 13:29Partial coverage0 min—
Tue 3 NovGouda 13:240 min—
Mon 2 NovGouda 13:290 min—
Sun 1 NovGouda 13:290 min—
Sat 31 OctGouda 13:280 min—
Fri 30 OctGouda 13:23No data—
Thu 29 OctGouda 13:300 min—
Wed 28 OctGouda 13:29Partial coverage0 min—
Tue 27 OctGouda 13:290 min—
Mon 26 OctGouda 13:280 min—
Fri 16 OctGouda 13:280 min—
Thu 15 OctGouda 13:300 min—
Wed 14 OctGouda 13:28Partial coverage0 min—
Tue 13 OctGouda 13:28No data—
Mon 12 OctGouda 13:290 min—
Sun 11 OctRotterdam Centraal 13:28No data—
Sat 10 OctGouda 13:30+3 min+3 min
Fri 9 OctGouda 13:29+1 min+1 min
Thu 8 OctRotterdam Centraal 13:30+3 min+3 min
Wed 7 OctGouda 13:29Partial coverage0 min—
Tue 6 OctGouda 13:290 min—
Mon 5 OctGouda 13:280 min—
Sun 4 OctGouda 13:35No data—
Sat 3 OctGouda 13:23No data—
Fri 2 OctGouda 13:23No data—
Thu 1 OctGouda 13:24No data—
Wed 30 SeptGouda 13:23No data—
Tue 29 SeptGouda 13:23No data—
Mon 28 SeptGouda 13:23No data—
Sun 27 SeptGouda 13:23No data—