Train NS 5738 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 12:11 → Leiden Centraal 13:39 Daily 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sassenheim at 13:48 No data

  1. Utrecht Centraal12:11
  2. Hilversum Sportpark12:27
  3. Bussum Zuid12:37
  4. Diemen Zuid13:00
  5. Amsterdam RAI13:06
  6. Sassenheim13:34
  7. Leiden Centraal13:39

Next service: tomorrow 12:11 from Utrecht Centraal · Sat 7 Nov

Next departure 12:11 tomorrow · Utrecht Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 12 full · 11 partial · 5 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 14 full · 12 partial · 59 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 Leiden 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
12:11on time on time
12:15≈ on time ≈ on time
12:23≈ on time ≈ on time
12:27≈ on time ≈ on time
12:30 / 12:31≈ on time ≈ on time
12:33≈ on time ≈ on time
12:37≈ on time ≈ on time
12:40≈ on time ≈ on time
12:46 / 12:53≈ on time ≈ on time
13:00≈ on time ≈ on time
13:02≈ on time ≈ on time
13:06≈ on time ≈ on time
13:09 / 13:10≈ on time ≈ on time
13:16 / 13:18≈ on time ≈ on time
13:22≈ on time ≈ on time
13:27≈ on time ≈ on time
13:34≈ on time ≈ on time
13:39on 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
Fri 6 NovSassenheim 13:48No data—
Thu 5 NovSassenheim 13:53Partial coverage0 min—
Wed 4 NovSassenheim 13:480 min—
Tue 3 NovSassenheim 13:49Partial coverage0 min—
Mon 2 NovSassenheim 13:49Partial coverage0 min—
Sun 1 NovHilversum Sportpark 12:390 min—
Sat 31 OctSchiphol Airport 13:320 min—
Fri 30 OctSassenheim 13:480 min—
Thu 29 OctSassenheim 13:54Partial coverage0 min—
Wed 28 OctSassenheim 13:490 min—
Tue 27 OctSassenheim 13:49No data—
Mon 26 OctSassenheim 13:50Partial coverage0 min—
Sun 25 OctSchiphol Airport 13:32No data—
Sat 24 OctSchiphol Airport 13:330 min—
Fri 23 OctSassenheim 13:480 min—
Thu 22 OctSassenheim 13:49Partial coverage0 min—
Wed 21 OctSassenheim 13:49No data—
Tue 20 OctSassenheim 13:49No data—
Mon 19 OctSassenheim 13:49Partial coverage0 min—
Fri 16 OctSassenheim 13:480 min—
Thu 15 OctSassenheim 13:51Partial coverage0 min—
Wed 14 OctSassenheim 13:500 min—
Tue 13 OctSassenheim 13:49Partial coverage0 min—
Mon 12 OctSassenheim 13:49Partial coverage0 min—
Sun 11 OctSchiphol Airport 13:320 min—
Sat 10 OctSchiphol Airport 13:320 min—
Fri 9 OctSassenheim 13:480 min—
Thu 8 OctSassenheim 13:49Partial coverage0 min—
Wed 7 OctSassenheim 13:490 min—
Tue 6 OctSassenheim 13:48Partial coverage0 min—