Train NS 5740 Utrecht Centraal – Leiden Centraal

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

✓ Today’s run finished

Today, last fix heading to Sassenheim at 14:19 0 min

  1. Utrecht Centraal12:41
  2. Hilversum Sportpark12:57
  3. Bussum Zuid13:07
  4. Diemen Zuid13:30
  5. Amsterdam RAI13:36
  6. Sassenheim14:04
  7. Leiden Centraal14:09

Next service: tomorrow 12:41 from Utrecht Centraal · Fri 6 Nov

Next departure 12:41 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 10 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 8 full · 12 partial · 65 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=2
  • 100% W n=4
  • 100% T n=4
  • 100% F n=2
  • 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, 20 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:41on time on time
12:45≈ on time ≈ on time
12:53≈ on time ≈ on time
12:57≈ on time ≈ on time
13:00 / 13:01≈ on time ≈ on time
13:03≈ on time ≈ on time
13:07≈ on time ≈ on time
13:10≈ on time ≈ on time
13:16 / 13:23≈ on time ≈ on time
13:30≈ on time ≈ on time
13:32≈ on time ≈ on time
13:36≈ on time ≈ on time
13:39 / 13:40≈ on time ≈ on time
13:46 / 13:48≈ on time ≈ on time
13:53≈ on time ≈ on time
13:57≈ on time ≈ on time
14:04≈ on time ≈ on time
14:09on 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 NovSassenheim 14:19Partial coverage0 min—
Wed 4 NovSassenheim 14:19Partial coverage0 min—
Tue 3 NovSassenheim 14:19No data—
Mon 2 NovSassenheim 14:19No data—
Sun 1 NovHilversum Sportpark 13:110 min—
Sat 31 OctSchiphol Airport 14:020 min—
Fri 30 OctSassenheim 14:18No data—
Thu 29 OctSassenheim 14:22Partial coverage0 min—
Wed 28 OctSassenheim 14:19Partial coverage0 min—
Tue 27 OctSassenheim 14:19Partial coverage0 min—
Mon 26 OctSassenheim 14:20Partial coverage0 min—
Sun 25 OctSchiphol Airport 14:02No data—
Sat 24 OctSchiphol Airport 14:020 min—
Fri 23 OctSassenheim 14:190 min—
Thu 22 OctSassenheim 14:19No data—
Wed 21 OctSassenheim 14:19Partial coverage0 min—
Tue 20 OctSassenheim 14:20No data—
Mon 19 OctSassenheim 14:19Partial coverage0 min—
Fri 16 OctSassenheim 14:20No data—
Thu 15 OctBussum Zuid 15:220 min—
Wed 14 OctSassenheim 14:19No data—
Tue 13 OctSassenheim 14:47No data—
Mon 12 OctSassenheim 14:20No data—
Sun 11 OctSchiphol Airport 14:020 min—
Sat 10 OctHilversum 14:510 min+29 min
Fri 9 OctSassenheim 14:180 min—
Thu 8 OctSassenheim 14:19Partial coverage0 min—
Wed 7 OctSassenheim 14:19Partial coverage0 min—
Tue 6 OctSassenheim 14:19Partial coverage0 min—
Mon 5 OctSassenheim 14:20Partial coverage+1 min+1 min