Train NS 2819 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 06:20 → Utrecht Centraal 06:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 06:59 No data

  1. Rotterdam Centraal06:20
  2. Rotterdam Alexander06:28
  3. Gouda06:38
  4. Utrecht Centraal06:57

Next service: tomorrow 06:20 from Rotterdam Centraal · Fri 6 Nov

Next departure 06:20 tomorrow · Rotterdam Centraal
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 11 full · 6 partial · 2 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 12 full · 6 partial · 39 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: +3 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

  • Wed 28 Oct Max en route +9 min · last fix heading to Gouda +9 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Rotterdam Centraal +3 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Gouda +3 min

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 83% · 15
  • 3–10 min 17% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 75% W n=4
  • 33% T n=3
  • 100% F n=3
  • 100% S n=2
  • — S n=0

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
06:20on time on time
06:28≈ on time ≈ on time
06:38 / 06:39≈ on time ≈ +1 min
06:57on 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
Thu 5 NovGouda 06:59No data—
Wed 4 NovGouda 06:59Partial coverage+1 min+1 min
Tue 3 NovGouda 06:580 min—
Mon 2 NovGouda 06:590 min—
Sat 31 OctGouda 07:040 min—
Fri 30 OctGouda Goverwelle 06:58+2 min+2 min
Thu 29 OctGouda 07:00Partial coverage+3 min+3 min
Wed 28 OctGouda 07:17Partial coverage+9 min+9 min
Tue 27 OctGouda 06:59+1 min+1 min
Mon 26 OctRotterdam Centraal 06:58No data—
Fri 16 OctGouda 06:590 min—
Thu 15 OctRotterdam Centraal 07:09+3 min+3 min
Wed 14 OctGouda 06:58Partial coverage0 min—
Tue 13 OctGouda 06:580 min—
Mon 12 OctGouda 06:580 min—
Sat 10 OctGouda 08:45+1 min+1 min
Fri 9 OctGouda 06:590 min—
Thu 8 OctGouda 06:59Partial coverage+1 min—
Wed 7 OctGouda 06:58Partial coverage0 min—
Tue 6 OctGouda 06:580 min—
Mon 5 OctGouda 06:54No data—
Sat 3 OctGouda 07:03No data—
Fri 2 OctGouda 07:08No data—
Thu 1 OctGouda 06:59No data—
Wed 30 SeptGouda 06:53No data—
Tue 29 SeptGouda 06:55No data—
Mon 28 SeptGouda 06:53No data—
Sat 26 SeptGouda 06:53No data—
Fri 25 SeptGouda 06:55No data—
Thu 24 SeptGouda 06:54No data—