Train NS 5744 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 13:41 → Leiden Centraal 15:09 Daily 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:41 from Utrecht Centraal · Thu 5 Nov

Next departure 13:41 today · Utrecht Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 8 full · 12 partial · 7 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 8 full · 14 partial · 62 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 Leiden 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

  • Sat 31 Oct Max en route +7 min · last fix heading to Schiphol Airport +6 min
  • Fri 9 Oct Max en route +6 min · last fix heading to Sassenheim +6 min

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 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 67% F n=3
  • 67% 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, 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
13:41on time on time
13:45≈ on time ≈ on time
13:53≈ on time ≈ +1 min
13:57≈ on time ≈ +1 min
14:00 / 14:01≈ on time ≈ +1 min
14:03≈ on time ≈ +1 min
14:07≈ on time ≈ +2 min
14:10≈ on time ≈ +2 min
14:16 / 14:23≈ on time ≈ +2 min
14:30≈ on time ≈ +3 min
14:32≈ on time ≈ +3 min
14:36≈ on time ≈ +4 min
14:39 / 14:40≈ on time ≈ +4 min
14:46 / 14:48≈ on time ≈ +4 min
14:53≈ on time ≈ +5 min
14:57≈ on time ≈ +5 min
15:04≈ on time ≈ +5 min
15:09on time +6 min

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
Wed 4 NovSassenheim 15:19Partial coverage0 min—
Tue 3 NovSassenheim 15:20No data—
Mon 2 NovSassenheim 15:19Partial coverage0 min—
Sun 1 NovSchiphol Airport 15:030 min—
Sat 31 OctSchiphol Airport 15:08+6 min+7 min
Fri 30 OctSassenheim 15:190 min—
Thu 29 OctSassenheim 15:19Partial coverage0 min—
Wed 28 OctSassenheim 15:19Partial coverage0 min—
Tue 27 OctSassenheim 15:19Partial coverage0 min—
Mon 26 OctSassenheim 15:19No data—
Sun 25 OctSchiphol Airport 15:03No data—
Sat 24 OctSchiphol Airport 15:030 min—
Fri 23 OctSassenheim 15:18No data—
Thu 22 OctSassenheim 15:19Partial coverage0 min—
Wed 21 OctSassenheim 15:19Partial coverage0 min—
Tue 20 OctSassenheim 15:19Partial coverage0 min—
Mon 19 OctSassenheim 15:20Partial coverage0 min—
Fri 16 OctSassenheim 15:180 min—
Thu 15 OctSassenheim 15:19No data—
Wed 14 OctSassenheim 15:19No data—
Tue 13 OctSassenheim 15:19Partial coverage0 min—
Mon 12 OctSassenheim 15:20No data—
Sun 11 OctSchiphol Airport 15:030 min—
Sat 10 OctSchiphol Airport 15:020 min—
Fri 9 OctSassenheim 15:24+6 min+6 min
Thu 8 OctSassenheim 15:18Partial coverage0 min—
Wed 7 OctSassenheim 15:19Partial coverage0 min—
Tue 6 OctSassenheim 15:19Partial coverage0 min—
Mon 5 OctSassenheim 15:20Partial coverage0 min—
Sun 4 OctAlmere Buiten 14:47No data—