Train NS 4989 Hilversum – Utrecht Centraal

Hilversum 00:47 → Utrecht Centraal 01:06 Daily 0 h 19 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:07 +1 min

  1. Hilversum00:47
  2. Hilversum Sportpark00:50
  3. Hollandsche Rading00:54
  4. Utrecht Overvecht01:02
  5. Utrecht Centraal01:06

Next service: tomorrow 00:47 from Hilversum · Sun 8 Nov

Next departure 00:47 tomorrow · Hilversum
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
00:47on time on time
00:50≈ on time ≈ on time
00:54≈ on time ≈ on time
01:02≈ on time ≈ on time
01:06on time on time

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 7 Nov— 01:07+1 min+1 min
Fri 6 Nov— 01:090 min—
Thu 5 Nov— 01:080 min—
Wed 4 Nov— 01:080 min—
Tue 3 Nov— 01:090 min—
Mon 2 NovUtrecht Overvecht 01:140 min—
Sun 1 Nov— 01:07No data—
Sat 31 Oct— 01:070 min—
Fri 30 Oct— 01:070 min—
Thu 29 Oct— 01:070 min—
Wed 28 Oct— 01:090 min—
Tue 27 Oct— 01:070 min—
Mon 26 OctUtrecht Overvecht 01:26No data—
Sun 25 Oct— 01:070 min—
Sat 24 Oct— 01:080 min—
Fri 23 Oct— 01:070 min—
Thu 22 Oct— 01:070 min—
Wed 21 Oct— 01:100 min—
Tue 20 Oct— 01:070 min—
Mon 19 OctUtrecht Overvecht 01:150 min—
Sun 18 OctUtrecht Overvecht 01:060 min—
Sat 17 Oct— 01:070 min—
Fri 16 Oct— 01:070 min—
Thu 15 Oct— 01:070 min—
Wed 14 Oct— 01:280 min—
Tue 13 Oct— 01:070 min—
Mon 12 OctUtrecht Overvecht 01:170 min—
Sun 11 Oct— 01:080 min—
Sat 10 Oct— 01:08+1 min—
Fri 9 Oct— 01:070 min—