Train NS 4263 Haarlem → Leiden Centraal

Haarlem 18:47 → Leiden Centraal 19:10 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

NS 4263 Haarlem–Leiden Centraal: final delay under 3 min on 22 of its 23 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 20:08 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Voorhout at 19:19 0 min

  1. Haarlem18:47
  2. Heemstede-Aerdenhout18:52
  3. Hillegom18:57
  4. Voorhout19:04
  5. Leiden Centraal19:10

Next service: tomorrow 18:47 from Haarlem · Mon 23 Nov

Next departure 18:47 tomorrow · Haarlem
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 16 full · 7 partial · 5 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 24 full · 9 partial · 29 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: +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

  • Thu 19 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
18:47on time on time
18:52≈ on time ≈ on time
18:57≈ on time ≈ +1 min
19:04≈ on time ≈ +1 min
19:10on 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
Sun 22 NovVoorhout 19:19Partial coverage0 min—
Sat 21 NovVoorhout 19:19Partial coverage0 min—
Fri 20 NovLeiden Centraal 19:340 min—
Thu 19 Nov— 19:39+3 min+3 min
Wed 18 Nov— 19:340 min—
Tue 17 Nov— 19:380 min—
Mon 16 Nov— 19:38+2 min+2 min
Fri 13 NovHillegom 19:340 min—
Thu 12 Nov— 19:340 min—
Wed 11 Nov— 19:340 min—
Tue 10 Nov— 19:340 min—
Mon 9 Nov— 19:340 min—
Sun 8 NovVoorhout 19:19Partial coverage0 min—
Sat 7 NovVoorhout 19:19Partial coverage0 min—
Fri 6 NovHaarlem 19:37+2 min+2 min
Thu 5 Nov— 19:34No data—
Wed 4 Nov— 19:34No data—
Tue 3 Nov— 19:34No data—
Mon 2 NovHaarlem 19:340 min—
Sun 1 NovVoorhout 19:19Partial coverage0 min—
Sat 31 OctVoorhout 19:19Partial coverage0 min—
Fri 30 OctHeemstede-Aerdenhout 19:060 min—
Thu 29 Oct— 19:350 min—
Wed 28 Oct— 19:350 min—
Tue 27 Oct— 20:260 min—
Mon 26 Oct— 19:37No data—
Sun 25 OctVoorhout 19:22No data—
Sat 24 OctVoorhout 19:22Partial coverage0 min—
Fri 23 OctDen Haag Mariahoeve 19:42+1 min—
Thu 22 Oct— 19:360 min—