Opposition · USPTO

Opposition 91297581

OtherUSPTO

Opposition 91297581 at USPTO between Meta Platforms, Inc. and Shenzhen Xinmaita Technology Co., Ltd., over the mark KOCULUS, filed Mar 12, 2025. Status in the office record: other.

View KOCULUSGet this data via the API
Status
Other
Result
Other
Filed
Mar 12, 2025
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Meta Platforms, Inc.

Company trademarks
Respondent

Shenzhen Xinmaita Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the KOCULUS filing.

  1. KOCULUS filed

    Application 98440339 filed at the USPTO.

  2. Opposition filed

    Meta Platforms, Inc. started opposition 91297581 at USPTO against KOCULUS.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
KOCULUSContested98440339USPTO
OCULUSRelied on86143192USPTO
OCULUSRelied on86757871USPTO
OCULUS READYRelied on87099848USPTO
OCULUS READYRelied on87099856USPTO
OCULUS GORelied on87641268USPTO
OCULUSRelied on87731331USPTO
OCULUS QUESTRelied on88132454USPTO
OCULUS INSIGHTRelied on88176086USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_6b6f7097-7c40-4739-8287-107d08580ec1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6b6f7097-7c40-4739-8287-107d08580ec1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91297581",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-03-12",
  "parties": [
    {
      "name": "Meta Platforms, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Xinmaita Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}