Train NS 2891 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 00:58 0 min

  1. Rotterdam Centraal00:20
  2. Rotterdam Alexander00:28
  3. Gouda00:38
  4. Utrecht Centraal00:57

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

Next departure 00:20 Monday · Rotterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 0 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 24 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
00:20on time on time
00:28≈ on time ≈ on time
00:38 / 00:39≈ on time ≈ on time
00: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
Sat 7 Nov— 00:580 min—
Fri 6 Nov— 00:590 min—
Thu 5 Nov— 00:590 min—
Wed 4 Nov— 00:590 min—
Tue 3 Nov— 00:590 min—
Mon 2 NovGouda 00:59Partial coverage0 min—
Sun 1 Nov— 01:150 min—
Sat 31 Oct— 01:010 min—
Fri 30 Oct— 01:160 min—
Thu 29 Oct— 00:580 min—
Wed 28 Oct— 00:580 min—
Tue 27 Oct— 00:580 min—
Sat 17 Oct— 00:59+1 min+1 min
Fri 16 Oct— 00:580 min—
Thu 15 Oct— 00:580 min—
Wed 14 Oct— 00:590 min—
Tue 13 Oct— 00:590 min—
Mon 12 OctGouda 00:580 min—
Sun 11 Oct— 01:000 min—
Sat 10 Oct— 00:580 min—
Fri 9 Oct— 00:580 min—
Thu 8 Oct— 00:580 min—
Wed 7 Oct— 00:580 min—
Tue 6 Oct— 00:580 min—
Mon 5 OctGouda 00:58No data—
Sun 4 OctRotterdam Alexander 00:42No data—
Mon 21 SeptGouda 00:53No data—
Mon 7 SeptGouda 00:54No data—
Mon 31 AugGouda 00:53No data—
Mon 10 AugGouda 00:53No data—