Train NS 5739 Leiden Centraal – Utrecht Centraal

Leiden Centraal 10:50 → Utrecht Centraal 12:18 Daily 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 10:50 from Leiden Centraal · Fri 13 Nov

Next departure 10:50 today · Leiden Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 13 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 7 full · 15 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

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

On-time by weekday

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

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
10:50on time on time
10:55≈ on time ≈ on time
11:02≈ on time ≈ on time
11:07≈ on time ≈ on time
11:11 / 11:13≈ on time ≈ on time
11:19 / 11:20≈ on time ≈ on time
11:22≈ on time ≈ on time
11:25 / 11:26≈ on time ≈ on time
11:29≈ on time ≈ on time
11:35 / 11:43≈ on time ≈ on time
11:49≈ on time ≈ on time
11:52≈ on time ≈ on time
11:56≈ on time ≈ on time
11:58 / 11:59≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:06≈ on time ≈ +1 min
12:14≈ on time ≈ +1 min
12:18on time +1 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
Thu 12 NovUtrecht Overvecht 12:28Partial coverage0 min—
Wed 11 NovUtrecht Overvecht 12:28Partial coverage0 min—
Tue 10 NovUtrecht Overvecht 12:29Partial coverage0 min—
Mon 9 NovUtrecht Overvecht 12:28Partial coverage0 min—
Sun 8 NovUtrecht Overvecht 12:280 min—
Sat 7 NovUtrecht Overvecht 12:280 min—
Fri 6 NovUtrecht Overvecht 12:29No data—
Thu 5 NovUtrecht Overvecht 12:28No data—
Wed 4 NovUtrecht Overvecht 12:29Partial coverage+1 min—
Tue 3 NovUtrecht Overvecht 12:28No data—
Mon 2 NovUtrecht Overvecht 12:28No data—
Sun 1 NovUtrecht Overvecht 12:320 min—
Sat 31 OctUtrecht Overvecht 12:280 min—
Fri 30 OctUtrecht Overvecht 12:28Partial coverage0 min—
Thu 29 OctUtrecht Overvecht 12:28Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 12:28No data—
Tue 27 OctUtrecht Overvecht 12:28Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 12:31No data—
Sun 25 OctUtrecht Overvecht 12:29No data—
Sat 24 OctUtrecht Overvecht 12:290 min—
Fri 23 OctUtrecht Overvecht 12:32No data—
Thu 22 OctUtrecht Overvecht 12:29No data—
Wed 21 OctUtrecht Overvecht 12:29No data—
Tue 20 OctUtrecht Overvecht 12:29No data—
Mon 19 OctUtrecht Overvecht 12:28Partial coverage0 min—
Fri 16 OctUtrecht Overvecht 12:39No data—
Thu 15 OctUtrecht Overvecht 12:28No data—
Wed 14 OctUtrecht Overvecht 12:28No data—
Tue 13 OctUtrecht Overvecht 12:29No data—
Mon 12 OctUtrecht Overvecht 12:28Partial coverage0 min—