Train NS 2279 Amsterdam Centraal – Delft Campus

Amsterdam Centraal 22:36 → Delft Campus 23:39 Daily 1 h 03 min · 9 stops NS (Nederlandse Spoorwegen)

Running now · updated 00:27

Heading to Delft Campus 0 min

Estimated arrival at Delft Campus 23:39

  1. Amsterdam Centraal22:36
  2. Amsterdam Sloterdijk22:41
  3. Heemstede-Aerdenhout22:58
  4. Leiden Centraal23:13
  5. Den Haag Laan v NOI23:23
  6. Delft23:36
  7. Delft Campus23:39

Today it is running no worse than usual: typical arrival delay is 0 min; 96% of the last 27 runs arrived on time.

On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 16 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 Delft Campus, 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 10 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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 10Today
22:36on time on time
22:41≈ on time ≈ on time
22:51 / 22:53≈ on time ≈ on time
22:58≈ on time ≈ on time
23:13 / 23:15≈ on time ≈ on time
23:23 / 23:24≈ on time ≈ on time
23:27 / 23:28≈ on time ≈ on time
23:36≈ on time ≈ on time
23: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 Nov— 00:240 min—
Thu 5 Nov— 00:290 min—
Wed 4 Nov— 00:290 min—
Tue 3 Nov— 00:490 min—
Mon 2 Nov— 00:330 min+1 min
Sun 1 NovDen Haag HS 00:290 min+4 min
Sat 31 OctLeiden Centraal 00:310 min—
Fri 30 Oct— 00:310 min—
Thu 29 Oct— 23:490 min—
Wed 28 Oct— 00:310 min—
Tue 27 Oct— 00:310 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctDordrecht 00:310 min—
Sat 24 OctAmsterdam Centraal 00:360 min—
Fri 23 Oct— 00:360 min+3 min
Thu 22 Oct— 00:31No data—
Wed 21 Oct— 00:34No data—
Tue 20 Oct— 00:310 min—
Mon 19 Oct— 00:310 min—
Sun 18 OctAmsterdam Sloterdijk 00:310 min—
Sat 17 OctDordrecht 00:340 min—
Fri 16 Oct— 00:360 min+7 min
Thu 15 Oct— 00:310 min—
Wed 14 Oct— 00:310 min—
Tue 13 Oct— 00:310 min—
Mon 12 Oct— 00:540 min—
Sun 11 OctDordrecht 00:310 min—
Sat 10 Oct— 23:48+5 min+6 min
Fri 9 Oct— 00:310 min+2 min
Thu 8 Oct— 00:310 min—