Train NS 5733 Leiden Centraal – Utrecht Centraal

Leiden Centraal 09:20 → Utrecht Centraal 10:48 Mon, Tue, Wed, Thu, Fri, Sat 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 10:58 0 min

  1. Leiden Centraal09:20
  2. Hoofddorp09:37
  3. Amsterdam RAI09:52
  4. Weesp10:05
  5. Bussum Zuid10:22
  6. Utrecht Overvecht10:44
  7. Utrecht Centraal10:48

Next service: tomorrow 09:20 from Leiden Centraal · Fri 6 Nov

Next departure 09:20 tomorrow · Leiden Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 4 full · 13 partial · 8 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 4 full · 14 partial · 61 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: +1 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

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to Utrecht Overvecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 50% F n=2
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 18 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:20on time on time
09:25— —
09:32— —
09:37— —
09:41 / 09:43— —
09:49 / 09:50— —
09:52— —
09:55 / 09:56— —
09:59— —
10:05 / 10:13— —
10:19— —
10:22— —
10:26— —
10:28 / 10:29— —
10:32— —
10:36— —
10:44— —
10: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
Thu 5 NovUtrecht Overvecht 10:58Partial coverage0 min—
Wed 4 NovUtrecht Overvecht 10:58Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 10:58No data—
Mon 2 NovUtrecht Overvecht 10:58No data—
Sat 31 OctUtrecht Overvecht 10:59+1 min+1 min
Fri 30 OctUtrecht Overvecht 10:59No data—
Thu 29 OctUtrecht Overvecht 10:58Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 10:58Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 10:58Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 10:59Partial coverage0 min—
Sat 24 OctUtrecht Overvecht 10:590 min—
Fri 23 OctBussum Zuid 11:17Partial coverage0 min—
Thu 22 OctUtrecht Overvecht 11:04No data—
Wed 21 OctUtrecht Overvecht 10:58Partial coverage0 min—
Tue 20 OctUtrecht Overvecht 10:58No data—
Mon 19 OctUtrecht Overvecht 10:58Partial coverage0 min—
Fri 16 OctUtrecht Overvecht 10:58No data—
Thu 15 OctUtrecht Overvecht 10:58Partial coverage0 min—
Wed 14 OctUtrecht Overvecht 10:59No data—
Tue 13 OctUtrecht Overvecht 10:59No data—
Mon 12 OctUtrecht Overvecht 10:58Partial coverage0 min—
Sat 10 OctUtrecht Overvecht 10:580 min—
Fri 9 OctUtrecht Overvecht 11:02Partial coverage+4 min+4 min
Thu 8 OctUtrecht Overvecht 10:58Partial coverage0 min—
Wed 7 OctUtrecht Overvecht 12:000 min—
Tue 6 OctUtrecht Overvecht 10:58Partial coverage0 min—
Mon 5 OctUtrecht Overvecht 10:59No data—
Sat 3 OctUtrecht Overvecht 10:58No data—
Fri 2 OctUtrecht Overvecht 10:58No data—
Thu 1 OctUtrecht Overvecht 10:58No data—