Record entry · Auto

Oppo

Added 8 Oct 2026Mentions 20Sources 9Days of coverage 13

Why this name is on the record

Oppo was added automatically on 8 Oct 2026 after 20 mentions across 9 sources over 13 days. 40% of that coverage came from a single subject area.

Who Oppo moves with

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

AIChinaAppleXiaomiSnapdragonAmazonAmoled
  • AI · 45 shared documents
  • Android · 44 shared documents · no page of its own yet
  • China · 42 shared documents
  • Apple · 40 shared documents
  • Xiaomi · 35 shared documents
  • Snapdragon · 34 shared documents
  • Amazon · 32 shared documents
  • Faqs · 32 shared documents · no page of its own yet
  • Amoled · 29 shared documents
  • Buy · 28 shared documents · no page of its own yet

For developers

GET https://sigb.ai/api/registry?slug=oppo

{
  "slug": "oppo",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "oppo",
    "promotedAt": "2026-10-08",
    "category": "auto",
    "evidence": {
      "mentions": 20,
      "sources": 9,
      "days": 13,
      "concentration": 0.4,
      "standAloneShare": 0.862
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Oppo

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

Oppo

Entity.

Evidence
69 documents · 22 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
Added automatically from coverage
Time
first seen 3 Sept 2026, last seen 8 Oct 2026
Measured
16% of mentions say something specific about it; the rest only name it
As of
8 Oct 2026
12 links from here

Who it moves with: the 10 names are in the map above.

What is claimed about it (2)

  • Single source: Reported by one source so far.

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this