Train NS 2211 Amsterdam Centraal – Delft Campus

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

Running now · updated 05:45

Heading to Delft Campus 0 min

Estimated arrival at Delft Campus 06:39 · 121 km/h

  1. Amsterdam Centraal05:36
  2. Amsterdam Sloterdijk05:41
  3. Heemstede-Aerdenhout06:00
  4. Leiden Centraal06:13
  5. Den Haag Laan v NOI06:23
  6. Delft06:36
  7. Delft Campus06:39

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

On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
On-time · 90 days
97%
60/62 runs under 3 min
RT coverage: 61 full · 1 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Vlissingen Souburg +5 min
  • Fri 2 Oct Max en route +4 min · last fix heading to Amsterdam Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 60
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=11
  • 100% W n=10
  • 100% T n=11
  • 82% F n=11
  • 100% S n=8
  • — S n=0

Stops and timetable

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

Last 90 days, 62 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
05:36on time on time
05:41≈ on time ≈ on time
05:51 / 05:53≈ on time ≈ +1 min
06:00≈ on time ≈ +1 min
06:13 / 06:15≈ on time ≈ +1 min
06:23 / 06:24≈ on time ≈ +2 min
06:27 / 06:28≈ on time ≈ +2 min
06:36≈ on time ≈ +2 min
06:39on time +2 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
Sat 7 NovAmsterdam Sloterdijk 05:44Partial coverage0 min—
Fri 6 NovVlissingen Souburg 08:53No data—
Thu 5 NovVlissingen Souburg 08:490 min—
Wed 4 NovVlissingen Souburg 08:490 min—
Tue 3 NovVlissingen Souburg 08:520 min—
Mon 2 NovVlissingen Souburg 08:490 min—
Sat 31 OctVlissingen Souburg 08:53+2 min+3 min
Fri 30 OctVlissingen Souburg 08:540 min+1 min
Thu 29 OctVlissingen Souburg 08:500 min—
Wed 28 OctVlissingen Souburg 08:500 min—
Tue 27 OctVlissingen Souburg 08:500 min—
Mon 26 OctVlissingen Souburg 08:500 min—
Sat 24 OctVlissingen Souburg 08:500 min—
Fri 23 OctVlissingen Souburg 08:520 min—
Thu 22 OctVlissingen Souburg 08:500 min—
Wed 21 OctVlissingen Souburg 08:500 min—
Tue 20 OctVlissingen Souburg 08:510 min—
Mon 19 OctVlissingen Souburg 08:500 min—
Sat 17 OctVlissingen Souburg 08:500 min—
Fri 16 OctVlissingen Souburg 08:500 min—
Thu 15 OctVlissingen Souburg 09:05+2 min+2 min
Wed 14 OctVlissingen Souburg 08:500 min—
Tue 13 OctVlissingen Souburg 08:550 min+5 min
Mon 12 OctVlissingen Souburg 08:500 min—
Sat 10 OctVlissingen Souburg 08:50+3 min+3 min
Fri 9 OctVlissingen Souburg 08:55+5 min+5 min
Thu 8 OctVlissingen Souburg 08:51+1 min+1 min
Wed 7 OctVlissingen Souburg 08:53+3 min+4 min
Tue 6 OctVlissingen Souburg 08:53+3 min+3 min
Mon 5 OctAmsterdam Centraal 11:560 min+2 min