Train NS 8193 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 00:35 → Hoofddorp 00:57 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:58 0 min

  1. Amsterdam Centraal00:35
  2. Amsterdam Sloterdijk00:40
  3. Amsterdam Lelylaan00:44
  4. Schiphol Airport00:50
  5. Hoofddorp00:57

Next service: tomorrow 00:35 from Amsterdam Centraal · Sun 8 Nov

Next departure 00:35 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 20 full · 3 partial · 3 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 7 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 Hoofddorp, 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

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

  • Early 0% · 0
  • On time 100% · 24
  • 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=4
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
00:35on time on time
00:40≈ on time ≈ on time
00:44≈ on time ≈ on time
00:50 / 00:53≈ on time ≈ on time
00:57on 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
Sat 7 Nov— 00:580 min—
Fri 6 Nov— 00:580 min—
Thu 5 Nov— 00:590 min—
Wed 4 Nov— 00:490 min—
Tue 3 Nov— 00:580 min—
Mon 2 NovSchiphol Airport 01:07Partial coverage0 min—
Sun 1 Nov— 00:58No data—
Sat 31 Oct— 00:580 min—
Thu 29 Oct— 00:580 min—
Wed 28 Oct— 00:500 min—
Tue 27 Oct— 00:580 min—
Mon 26 OctSchiphol Airport 01:07Partial coverage0 min—
Sun 25 Oct— 00:58No data—
Sat 24 Oct— 00:590 min—
Fri 23 Oct— 00:590 min—
Thu 22 Oct— 00:580 min—
Wed 21 Oct— 00:500 min—
Tue 20 Oct— 00:590 min—
Mon 19 OctSchiphol Airport 01:07Partial coverage0 min—
Sun 18 OctSchiphol Airport 01:05No data—
Sat 17 Oct— 00:580 min—
Fri 16 Oct— 00:580 min—
Thu 15 Oct— 00:580 min—
Wed 14 Oct— 00:510 min—
Tue 13 Oct— 00:590 min—
Sat 10 Oct— 00:580 min—
Wed 7 Oct— 00:500 min—
Mon 21 SeptSchiphol Airport 01:07No data—
Thu 10 SeptSchiphol Airport 01:09No data—
Mon 7 SeptSchiphol Airport 01:07No data—