Train NS 5750 Utrecht Centraal → Hilversum

Utrecht Centraal 15:25 → Hilversum 15:41 Daily 0 h 16 min · 4 stops NS (Nederlandse Spoorwegen)

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

✓ Today’s run finished

Today, last fix heading to Hilversum Sportpark at 15:54 0 min

  1. Utrecht Centraal15:25
  2. Utrecht Overvecht15:29
  3. Hilversum Sportpark15:39
  4. Hilversum15:41

Next service: tomorrow 15:25 from Utrecht Centraal · Mon 23 Nov

Next departure 15:25 tomorrow · Utrecht Centraal
On-time · 30 days
82%
18/22 runs under 3 min
RT coverage: 20 full · 2 partial · 8 no data
On-time · 90 days
89%
32/36 runs under 3 min
RT coverage: 34 full · 2 partial · 51 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: +4 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

  • Sat 14 Nov Max en route +18 min · last fix heading to Schiphol Airport +17 min
  • Fri 20 Nov Max en route +14 min · last fix heading to Sassenheim +14 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Sassenheim +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 32
  • 3–10 min 6% · 2
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 36 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
15:25on time on time
15:29≈ on time ≈ +1 min
15:39≈ on time ≈ +2 min
15:41on 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
Sun 22 NovHilversum Sportpark 15:54Partial coverage0 min—
Sat 21 NovHilversum Sportpark 15:53Partial coverage0 min—
Fri 20 NovSassenheim 16:59+14 min+14 min
Thu 19 NovSassenheim 16:50+1 min+1 min
Wed 18 NovSassenheim 16:490 min+1 min
Tue 17 NovSassenheim 16:490 min—
Mon 16 NovSassenheim 16:54+4 min+4 min
Sun 15 NovSchiphol Airport 16:33+3 min+3 min
Sat 14 NovSchiphol Airport 16:49+17 min+18 min
Fri 13 NovSassenheim 16:480 min—
Thu 12 NovSassenheim 16:490 min—
Wed 11 NovSassenheim 16:490 min—
Tue 10 NovSassenheim 16:490 min—
Mon 9 NovSassenheim 16:490 min—
Sun 8 NovSchiphol Airport 16:330 min—
Sat 7 NovSchiphol Airport 16:320 min—
Fri 6 NovSassenheim 16:49No data—
Thu 5 NovSassenheim 16:49No data—
Wed 4 NovSassenheim 16:490 min—
Tue 3 NovSassenheim 16:49No data—
Mon 2 NovSassenheim 16:490 min—
Sun 1 NovSchiphol Airport 16:330 min—
Sat 31 OctSchiphol Airport 16:320 min—
Fri 30 OctSassenheim 16:48No data—
Thu 29 OctSassenheim 16:490 min—
Wed 28 OctSassenheim 16:48No data—
Tue 27 OctSassenheim 16:49No data—
Mon 26 OctSassenheim 16:49No data—
Sun 25 OctSchiphol Airport 16:32No data—
Sat 24 OctSchiphol Airport 16:320 min—