Train NS 5767 Hilversum → Utrecht Centraal

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

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

It has not run yet today

Last recorded run: Saturday 21 November 0 min

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

Next departure 19:18 today · Hilversum
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 22 full · 1 partial · 6 no data
On-time · 90 days
88%
28/32 runs under 3 min
RT coverage: 31 full · 1 partial · 53 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: +4 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

  • Mon 16 Nov Max en route +6 min · last fix heading to Duivendrecht +6 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Amsterdam RAI +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Duivendrecht +5 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Nieuw Vennep +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 28
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=5
  • 25% T n=4
  • 100% F n=5
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 32 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
19:18on time on time
19:21≈ on time ≈ +1 min
19:31≈ on time ≈ +2 min
19:35on 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 NovUtrecht Overvecht 19:44Partial coverage0 min—
Fri 20 NovUtrecht Overvecht 19:280 min+2 min
Thu 19 NovDuivendrecht 19:19+5 min+5 min
Wed 18 NovWeesp 19:19+3 min+3 min
Tue 17 NovAmsterdam RAI 19:19+1 min+2 min
Mon 16 NovDuivendrecht 19:30+6 min+6 min
Sun 15 NovUtrecht Overvecht 19:29+1 min+1 min
Sat 14 NovUtrecht Overvecht 19:280 min—
Fri 13 NovHilversum Media Park 19:19+1 min+1 min
Thu 12 NovAmsterdam RAI 19:28+6 min+6 min
Wed 11 NovSchiphol Airport 19:19+2 min+2 min
Tue 10 NovAmsterdam Zuid 18:340 min—
Mon 9 NovSchiphol Airport 19:190 min+2 min
Sun 8 NovUtrecht Overvecht 19:280 min—
Sat 7 NovUtrecht Overvecht 19:280 min—
Fri 6 NovWeesp 19:190 min—
Thu 5 NovSchiphol Airport 19:19No data—
Wed 4 NovSchiphol Airport 19:19No data—
Tue 3 NovHoofddorp 19:190 min—
Mon 2 NovHoofddorp 19:190 min—
Sun 1 NovUtrecht Overvecht 19:280 min—
Sat 31 OctUtrecht Overvecht 19:280 min—
Fri 30 OctBussum Zuid 19:21No data—
Thu 29 OctNieuw Vennep 19:21+3 min+3 min
Wed 28 OctSchiphol Airport 19:200 min—
Tue 27 OctNieuw Vennep 19:20No data—
Mon 26 OctHoofddorp 19:210 min—
Sun 25 OctUtrecht Overvecht 19:28No data—
Sat 24 OctUtrecht Overvecht 19:35No data—
Fri 23 OctUtrecht Overvecht 19:280 min—