The methodology behind compliance scores assigned to every entity on the KRUX network. Published in plain language, intentionally short, available to every party who points at a KTIN.
The KRUX Compliance Score is a number between 0 and 100 assigned to every entity on the network. It reflects all verified shipment activity recorded against an entity's KTIN. Scores are recomputed nightly at 22:00 UTC (midnight East Africa Time).
Scores unlock after an entity has tracked a minimum of 5 shipments. Below that threshold, the public verification page displays "Score pending" instead of a number.
The score is not a credit rating. It is a measure of the entity's trade-clearance record. It cannot be purchased, escalated, or fast-tracked. It can only be earned through clearances.
Two components contribute to the score. The clearance rate is the dominant factor; the clearance speed is the modifier.
Scores are mapped to four tiers. Tiers are published on the KTIN verification page; banks, regulators, and counterparties use them as a shorthand for the score.
A tier change requires a sustained shift in the underlying clearance record. A single late shipment will not drop an entity from Gold to Silver. We publish the exact thresholds because the score should be predictable.
An entity with 23 shipments tracked on the network, 21 cleared successfully, and an average clearance time of 11 days.
| Clearance rate · 21 / 23 | 91.3% |
| Rate component · 91.3% × 75 | 68 pts |
| Average clearance time | 11 days |
| Speed component · 8–14 day bracket | 18 pts |
| KRUX Compliance Score | 86 · PLATINUM |
This entity sits at the top of the Platinum band. One additional missed clearance would drop the rate component to ~65, bringing the total to 83 and the tier to Gold.
Before any clearance contributes to the score, KRUX calculates the regulatory window for the shipment. The window engine is the same model used by every workspace and by the public terminal.
The window status for a shipment is computed against three inputs:
The three resulting statuses are reported as:
SLA figures used by the window engine reflect each regulator's stated processing window as of 1 May 2026. KRUX recalculates against the regulator's current published procedure at runtime — the regulator's procedure governs in all cases.
The score is recalculated nightly at 22:00 UTC using all shipment activity logged to the entity's KTIN through 21:59 UTC of that day. Activity logged after the cutoff is included in the following night's batch.
The recalculation reads from the immutable shipment ledger, never from a derived cache. Every score change is traceable to a specific clearance event with a timestamp and the regulator's reference number.
An entity's score is never adjusted manually. If you believe a score is incorrect, file an appeal under §07. We will not silently move a number.
Any entity may appeal a score within 30 days of a recalculation. Appeals are filed at appeals@kruxvon.com and must cite the specific clearance event in dispute.
KRUX investigates by cross-referencing the entity's record with the relevant regulator's submission log. Outcomes are published as a public correction on the entity's KTIN verification page, with a dated note. The score adjustment, if any, is applied at the next nightly recalculation.
An entity has the right to dispute, but not to redact. The KTIN record is permanent.
The methodology described here is v1.0 — Issue 001 — published 1 May 2026.
Any material change to the scoring components, tier thresholds, or window engine constants will be published as a new versioned document and notified to every KTIN holder at least 30 days before it takes effect. Historic scores are not retroactively recalculated under a new methodology.
This document is the long-form companion to every KTIN verification page and to the public terminal at the homepage. It is the position from which every score on the KRUX network is computed.
If you find a part of this methodology that is unclear, or a case it does not cover, we want to know.