SCC Nexus · Companies House V4May 2026 · Public redacted intelligence · Run 26466028649
Multi-layer forensic intelligence

Companies House V4 Forensic Intelligence

National screen, priority risk universe, API enrichment and evidence-led reporting.

National screenMethodology
Dataset scanned5,698,175Companies House rows
Active universe5,168,399Open/active records after status exclusions
Forensic filtered3,693,966Review-indicator / ranked universe
Priority exported150,000Risk-ranked output set
API enriched100Companies House targeted calls

Forensic accounting

Risk scoring, charge/lender exposure, accounts status and officer churn are combined as review-priority signals.

Scientific controls

Validation, source hashes and output manifests support reproducibility.

Market intelligence

Sector and regional corporate-stress signals support research, not investment advice.

Executive narrative

May 2026 public briefing summarising Companies House review-priority indicators. The public site is redacted and pseudonymised; it is intended for research and triage, not allegations, credit decisions, investment advice or legal findings.

Risk populations

  • 5,168,399 active companies in the current public universe.
  • 3,693,966 records have one or more review-priority indicators.
  • 141,069 companies are flagged as at-risk within the public current screen.
  • 6,878 high-risk and 35 critical-risk records are retained for controlled review.

Industry and filing themes

  • The largest SIC concentrations include real estate, property trading, management consultancy and business-support activities.
  • A material subset of companies have no SIC supplied, which remains a quality-control and interpretation issue.
  • Accounts and confirmation-statement timeliness remain central review-priority signals.

Geographic concentration

  • The strongest registration clusters remain concentrated in London and other high-volume registered-office locations.
  • Public reporting should continue to use aggregate address clusters and postcode districts rather than naming individual companies in risk context.
  • Protected operational dashboards retain fuller fields for authorised review.

Controls and provenance

  • Monthly snapshots, source hashes, validation modules and archived artefacts are retained.
  • Public payloads should expose pseudonymised companies and aggregated clusters only.
  • Protected unredacted outputs remain separated under the access-controlled dashboard.