| Station | Late ≥3m | Cancelled | Avg s | Max s |
|---|
| Train | Type | Route | Delay s |
|---|
Each root train was the first to delay at its station; downstream trains arrived later with their own delays. Confidence is heuristic — not a verdict.
Grouped by dossier number. The longest-running incidents are surfaced first — these are the chronic problems hiding behind "new disruption" updates.
Lead time is planned departure minus modification timestamp. Negative = cancelled after the train should have departed. The lower, the more painful for passengers.
| Train | Station | Cause | Lead (min) | When |
|---|
Every DVS departure naming a MaterieelDeelNummer becomes one observation. The unit at the top is the physical asset NS leaned on hardest in the window. Click a row for the recent appearances timeline.
| Unit | Type | Observed | Trains | Days | Avg delay |
|---|
6-digit train numbers in the spec substitute ranges (100k–199k, 200k–299k, 300k–399k, 690k–699k, 700k–749k). Rescue = parent train was cancelled and the substitute took over. Extra = WijzigingType 24 disqualifier present, this is a genuinely added service. Orphan = substitute number with no matching parent cancellation observed (usually a data lag).
| Substitute | Status | Parent | Cause | Units | Last seen |
|---|
NDOV's own flag for material/service mismatches. Type 80 = an Intercity service is being run with Sprinter material. Type 81 = a Sprinter service is being run with IC material. Cross-referenced with the units actually observed on the train so each row tells the full story.
| Train | Direction | Units observed | Cause | When |
|---|