Train NS 5771 Hilversum → Utrecht Centraal

Hilversum 20:18 → Utrecht Centraal 20:35 Daily 0 h 17 min · 4 stops NS (Nederlandse Spoorwegen)

NS 5771 Hilversum–Utrecht Centraal: final delay under 3 min on 20 of its 22 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:28 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 20:18 from Hilversum · Sun 22 Nov

Next departure 20:18 today · Hilversum
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 7 no data
On-time · 90 days
91%
31/34 runs under 3 min
RT coverage: 33 full · 1 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Sun 15 Nov Max en route +6 min · last fix heading to Utrecht Overvecht +6 min
  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Utrecht Overvecht +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 31
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 75% W n=4
  • 100% T n=4
  • 100% F n=6
  • 83% S n=6
  • 75% S n=4

Stops and timetable

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

Last 90 days, 34 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
20:18on time on time
20:21≈ on time ≈ on time
20:31≈ on time ≈ +1 min
20:35on 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
Sat 21 NovUtrecht Overvecht 20:44Partial coverage0 min—
Fri 20 NovSchiphol Airport 20:190 min—
Thu 19 Nov— 20:190 min—
Wed 18 Nov— 19:090 min—
Tue 17 Nov— 20:190 min—
Mon 16 Nov— 20:190 min—
Sun 15 NovUtrecht Overvecht 20:32+6 min+6 min
Sat 14 NovUtrecht Overvecht 20:280 min—
Fri 13 NovSassenheim 20:19+1 min—
Thu 12 Nov— 20:190 min—
Wed 11 Nov— 20:190 min—
Tue 10 Nov— 19:330 min—
Mon 9 Nov— 20:190 min—
Sun 8 NovUtrecht Overvecht 20:280 min—
Sat 7 NovUtrecht Overvecht 20:280 min—
Fri 6 Nov— 20:190 min—
Thu 5 Nov— 20:20No data—
Wed 4 Nov— 20:24+5 min+5 min
Tue 3 Nov— 20:19No data—
Mon 2 Nov— 20:190 min—
Sun 1 NovUtrecht Overvecht 20:280 min—
Sat 31 OctUtrecht Overvecht 20:280 min—
Fri 30 OctLeiden Centraal 20:20No data—
Thu 29 Oct— 20:190 min—
Wed 28 Oct— 20:27No data—
Tue 27 Oct— 20:20No data—
Mon 26 OctNaarden-Bussum 20:19No data—
Sun 25 OctUtrecht Overvecht 20:28No data—
Sat 24 OctHollandsche Rading 20:470 min—
Fri 23 OctDuivendrecht 20:190 min—