Train NS 5721 Hoofddorp – Utrecht Centraal

Hoofddorp 06:37 → Utrecht Centraal 07:48 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 07:59 No data

  1. Hoofddorp06:37
  2. Amsterdam Zuid06:49
  3. Diemen Zuid06:59
  4. Naarden-Bussum07:19
  5. Hilversum Media Park07:26
  6. Utrecht Overvecht07:44
  7. Utrecht Centraal07:48

Next service: Monday 06:37 from Hoofddorp · Mon 9 Nov

Next departure 06:37 Monday · Hoofddorp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 1 full · 19 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 1 full · 21 partial · 50 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
06:37on time on time
06:41 / 06:43— —
06:49 / 06:50— —
06:52— —
06:55 / 06:56— —
06:59— —
07:05 / 07:13— —
07:19— —
07:22— —
07:26— —
07:28 / 07:29— —
07:32— —
07:36— —
07:44— —
07:48— —

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
Fri 6 NovUtrecht Overvecht 07:59No data—
Thu 5 NovUtrecht Overvecht 08:04No data—
Wed 4 NovUtrecht Overvecht 07:58Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 07:59Partial coverage0 min—
Mon 2 NovUtrecht Overvecht 07:59Partial coverage0 min—
Fri 30 OctUtrecht Overvecht 07:59Partial coverage0 min—
Thu 29 OctUtrecht Overvecht 07:59Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 07:580 min—
Tue 27 OctUtrecht Overvecht 07:58Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 07:58Partial coverage0 min—
Fri 23 OctUtrecht Overvecht 07:58Partial coverage0 min—
Thu 22 OctUtrecht Overvecht 08:03Partial coverage0 min—
Wed 21 OctUtrecht Overvecht 08:00Partial coverage0 min—
Tue 20 OctUtrecht Overvecht 08:01Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 08:02Partial coverage0 min—
Fri 16 OctUtrecht Overvecht 07:58Partial coverage0 min—
Thu 15 OctUtrecht Overvecht 07:58Partial coverage0 min—
Wed 14 OctUtrecht Overvecht 07:58Partial coverage0 min—
Tue 13 OctUtrecht Overvecht 07:58Partial coverage0 min—
Mon 12 OctUtrecht Overvecht 07:58Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 07:58Partial coverage0 min—
Thu 8 OctUtrecht Overvecht 07:58Partial coverage0 min—
Wed 7 OctUtrecht Overvecht 07:59Partial coverage0 min—
Tue 6 OctUtrecht Overvecht 07:58Partial coverage0 min—
Mon 5 OctUtrecht Overvecht 08:04No data—
Fri 2 OctUtrecht Overvecht 07:58No data—
Thu 1 OctUtrecht Overvecht 07:58No data—
Wed 30 SeptUtrecht Overvecht 07:58No data—
Tue 29 SeptUtrecht Overvecht 07:58No data—
Mon 28 SeptUtrecht Overvecht 07:58No data—