Train NS 5756 Utrecht Centraal → Hilversum

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

NS 5756 Utrecht Centraal–Hilversum: final delay under 3 min on 22 of its 25 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:05 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +1 min

Next service: today 16:55 from Utrecht Centraal · Sun 22 Nov

Next departure 16:55 today · Utrecht Centraal
On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 24 full · 1 partial · 4 no data
On-time · 90 days
82%
28/34 runs under 3 min
RT coverage: 33 full · 1 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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 16 Nov Max en route +21 min · last fix heading to Sassenheim +21 min
  • Sat 10 Oct Max en route +11 min · last fix heading to Schiphol Airport +11 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Schiphol Airport +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Sassenheim +5 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Sassenheim +4 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 82% · 28
  • 3–10 min 12% · 4
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 75% T n=4
  • 100% W n=4
  • 80% T n=5
  • 100% F n=5
  • 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
16:55on time on time
16:59≈ on time ≈ +1 min
17:09≈ on time ≈ +4 min
17:11on time +5 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 17:24Partial coverage+1 min+1 min
Fri 20 NovSassenheim 18:18+1 min+1 min
Thu 19 NovSassenheim 18:18+3 min+3 min
Wed 18 NovSassenheim 18:180 min—
Tue 17 NovSassenheim 18:18+1 min+1 min
Mon 16 NovSassenheim 18:49+21 min+21 min
Sun 15 NovSchiphol Airport 18:03+5 min+5 min
Sat 14 NovSchiphol Airport 18:020 min—
Fri 13 NovSassenheim 18:18+2 min+2 min
Thu 12 NovSassenheim 18:18+1 min—
Wed 11 NovSassenheim 18:180 min—
Tue 10 NovSassenheim 18:180 min—
Mon 9 NovSassenheim 18:180 min—
Sun 8 NovSchiphol Airport 18:020 min+1 min
Sat 7 NovSchiphol Airport 18:020 min—
Fri 6 NovSassenheim 18:180 min—
Thu 5 NovSassenheim 18:180 min—
Wed 4 NovSassenheim 18:18No data—
Tue 3 NovSassenheim 18:18No data—
Mon 2 NovSassenheim 18:18No data—
Sun 1 NovSchiphol Airport 18:020 min—
Sat 31 OctSchiphol Airport 18:020 min—
Fri 30 OctSassenheim 18:180 min—
Thu 29 OctNieuw Vennep 18:110 min—
Wed 28 OctSassenheim 18:180 min—
Tue 27 OctSassenheim 18:480 min—
Mon 26 OctSassenheim 18:180 min—
Sun 25 OctSchiphol Airport 18:02No data—
Sat 24 OctSchiphol Airport 18:040 min—
Fri 23 OctSassenheim 18:21No data—