Train NS 28516

Fri NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 16 October 0 min

The mini-map returns when the train runs
On-time ยท 30 days
โ€”
Too little data (1/1 runs with data)
RT coverage: 1 full ยท 0 partial ยท 0 no data
On-time ยท 90 days
โ€”
Too little data (1/9 runs with data)
RT coverage: 1 full ยท 0 partial ยท 8 no data
Typical delay
โ€”
Needs at least 5 runs with data (1 so far)
P90
โ€”
Needs at least 5 runs with data (1 so far)

Last 30 days

Delay at the end of each run, 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

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

  • Early 0% ยท 0
  • On time 100% ยท 1
  • 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
  • โ€” S n=0

Recent runs

DateLast stopFinalMax
Fri 16 OctDen Helder Zuid 08:210 minโ€”
Sun 20 SeptGeldermalsen 08:08No dataโ€”
Sat 19 SeptGeldermalsen 08:08No dataโ€”
Sat 12 SeptGouda 07:23No dataโ€”
Thu 27 AugDelft 08:08No dataโ€”
Wed 26 AugDelft 08:07No dataโ€”
Tue 25 AugDelft 08:17No dataโ€”
Sat 22 AugAmsterdam Zuid 07:30No dataโ€”
Sat 8 AugAmsterdam Amstel 08:52No dataโ€”

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.