Train NS 28721 Hoofddorp – Amersfoort Vathorst

Hoofddorp 06:37 → Amersfoort Vathorst 08:07 1 h 30 min · 15 stops NS (Nederlandse Spoorwegen)

Not running right now

Last recorded run: Sunday 1 November 0 min

On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 1 full · 1 partial · 0 no data
On-time · 90 days
—
Too little data (2/10 runs with data)
RT coverage: 1 full · 1 partial · 8 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 so far)

Last 30 days

Arrival delay at Amersfoort Vathorst, 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=1
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Not enough runs yet to work out the usual delay by stop.

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.

Recent runs

DateLast stopFinalMax
Sun 1 NovAmersfoort Schothorst 08:18Partial coverage0 min—
Fri 30 OctBlerick 09:110 min—
Sun 4 OctVlissingen Souburg 10:24No data—
Sat 3 OctVlissingen Souburg 10:24No data—
Fri 2 OctVlissingen Souburg 10:24No data—
Sun 13 SeptDe Vink 06:38No data—
Sat 12 SeptDe Vink 06:38No data—
Sat 15 AugHouten 07:05No data—
Thu 13 AugCulemborg 07:16No data—
Wed 12 AugCulemborg 07:16No data—
Tue 11 AugCulemborg 07:16No data—