Train NS 5764 Utrecht Centraal → Hilversum

Utrecht Centraal 18:55 → Hilversum 19:11 Daily 0 h 16 min · 4 stops NS (Nederlandse Spoorwegen)

NS 5764 Utrecht Centraal–Hilversum: final delay under 3 min on 19 of its 22 runs with data in the last 30 days (86%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 21:17 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Hilversum Sportpark at 19:25 +2 min

  1. Utrecht Centraal18:55
  2. Utrecht Overvecht18:59
  3. Hilversum Sportpark19:09
  4. Hilversum19:11

Next service: tomorrow 18:55 from Utrecht Centraal · Sun 22 Nov

Next departure 18:55 tomorrow · Utrecht Centraal
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 21 full · 1 partial · 6 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 32 full · 1 partial · 31 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 Hilversum, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 5 Oct Max en route +9 min · last fix heading to — +9 min
  • Wed 18 Nov Max en route +6 min · last fix heading to Utrecht Centraal +6 min
  • Thu 12 Nov Max en route +4 min · last fix heading to — +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 12% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 80% W n=5
  • 80% T n=5
  • 100% F n=5
  • 100% S n=5
  • 67% S n=3

Stops and timetable

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

Last 90 days, 33 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
18:55on time on time
18:59≈ on time ≈ +1 min
19:09≈ on time ≈ +3 min
19:11on time +3 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 NovHilversum Sportpark 19:25Partial coverage+2 min+2 min
Fri 20 NovNaarden-Bussum 19:540 min—
Thu 19 Nov— 19:530 min—
Wed 18 NovUtrecht Centraal 20:04+6 min+6 min
Tue 17 Nov— 19:530 min—
Mon 16 Nov— 19:090 min—
Sun 15 NovSchiphol Airport 20:03+3 min+3 min
Sat 14 NovSchiphol Airport 20:02+1 min+1 min
Fri 13 NovHilversum Sportpark 19:54+1 min+2 min
Thu 12 Nov— 19:59+4 min+4 min
Wed 11 Nov— 19:54+2 min+2 min
Tue 10 Nov— 19:180 min—
Mon 9 Nov— 19:540 min—
Sat 7 NovSchiphol Airport 20:020 min+2 min
Fri 6 NovUtrecht Overvecht 19:540 min—
Thu 5 Nov— 19:58No data—
Wed 4 Nov— 19:540 min—
Tue 3 Nov— 19:53No data—
Sun 1 NovSchiphol Airport 20:020 min—
Sat 31 OctSchiphol Airport 20:020 min—
Fri 30 OctHollandsche Rading 19:57No data—
Thu 29 Oct— 19:550 min—
Wed 28 Oct— 19:020 min—
Tue 27 Oct— 19:560 min—
Mon 26 OctSchiphol Airport 19:53No data—
Sun 25 OctSchiphol Airport 20:02No data—
Sat 24 OctSchiphol Airport 20:03No data—
Fri 23 OctWeesp 19:530 min—
Thu 22 OctUtrecht Overvecht 20:060 min—
Wed 21 Oct— 19:59No data—