Train NS 7435 Uitgeest – Utrecht Centraal

Uitgeest 09:33 → Utrecht Centraal 10:50 Mon, Tue, Wed, Thu, Fri 1 h 17 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Zuilen at 10:59 No data

  1. Uitgeest09:33
  2. Zaandijk Zaanse Schans09:49
  3. Amsterdam Sloterdijk10:01
  4. Amsterdam Amstel10:18
  5. Amsterdam Bijlmer ArenA10:24
  6. Utrecht Zuilen10:47
  7. Utrecht Centraal10:50

Next service: tomorrow 09:33 from Uitgeest · Fri 6 Nov

Next departure 09:33 tomorrow · Uitgeest
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 10 full · 3 partial · 9 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 48 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
09:33on time on time
09:38≈ on time ≈ on time
09:40 / 09:46≈ on time ≈ on time
09:49≈ on time ≈ on time
09:52≈ on time ≈ on time
09:55≈ on time ≈ on time
10:01≈ on time ≈ on time
10:07 / 10:09≈ on time ≈ on time
10:14≈ on time ≈ on time
10:18≈ on time ≈ on time
10:21≈ on time ≈ on time
10:24≈ on time ≈ on time
10:26≈ on time ≈ on time
10:30≈ on time ≈ on time
10:37≈ on time ≈ on time
10:42≈ on time ≈ on time
10:47≈ on time ≈ on time
10:50on 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
Thu 5 NovUtrecht Zuilen 10:59No data—
Wed 4 NovUtrecht Zuilen 10:59Partial coverage0 min—
Tue 3 NovUtrecht Zuilen 10:59No data—
Mon 2 NovUtrecht Zuilen 10:59No data—
Fri 30 OctUtrecht Zuilen 11:050 min—
Thu 29 OctUtrecht Zuilen 11:060 min—
Wed 28 OctUtrecht Zuilen 11:01No data—
Tue 27 OctUtrecht Zuilen 11:01No data—
Mon 26 OctUtrecht Zuilen 11:010 min—
Fri 23 OctUtrecht Zuilen 11:010 min—
Thu 22 OctAmsterdam Sloterdijk 10:17No data—
Wed 21 OctUtrecht Zuilen 11:03No data—
Tue 20 OctUtrecht Zuilen 11:200 min—
Mon 19 OctUtrecht Zuilen 11:05Partial coverage0 min—
Fri 16 OctUtrecht Zuilen 11:050 min—
Thu 15 OctUtrecht Zuilen 11:05No data—
Wed 14 OctUtrecht Zuilen 11:01No data—
Tue 13 OctUtrecht Zuilen 11:010 min—
Mon 12 OctUtrecht Zuilen 11:010 min—
Fri 9 OctUtrecht Zuilen 11:060 min—
Thu 8 OctUtrecht Zuilen 11:01Partial coverage0 min—
Wed 7 OctAmsterdam Holendrecht 12:010 min—
Tue 6 OctUtrecht Zuilen 11:01Partial coverage0 min—
Mon 5 OctEde-Wageningen 11:43No data—
Fri 2 OctUtrecht Zuilen 11:06No data—
Thu 1 OctUtrecht Zuilen 11:01No data—
Wed 30 SeptUtrecht Zuilen 11:11No data—
Tue 29 SeptUtrecht Zuilen 11:02No data—
Mon 28 SeptUtrecht Zuilen 11:01No data—
Fri 25 SeptUtrecht Zuilen 11:06No data—