Opposition · USPTO

Opposition 91299309

OtherUSPTO

Opposition 91299309 at USPTO between Chapter 4 Corp. and Guangzhou Nanhan Technology Co., Ltd., over the mark SUPDEVICE, filed May 29, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
May 29, 2025
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Chapter 4 Corp.

Respondent

Guangzhou Nanhan Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the SUPDEVICE filing.

  1. SUPDEVICE filed

    Application 98695796 filed at the USPTO.
  2. Opposition filed

    Chapter 4 Corp. started opposition 91299309 at USPTO against SUPDEVICE.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
SUPDEVICEContested98695796USPTO
SUPREMERelied on85424627USPTO
SUPREMERelied on85424722USPTO
SUPREMERelied on85868093USPTO
SUPREMERelied on85868116USPTO
SUPREMERelied on86225786USPTO
SUPREMERelied on86225846USPTO
SUPREMERelied on86225879USPTO
SUPREMERelied on86225910USPTO
SUPREMERelied on86691471USPTO
SUPREMERelied on86691492USPTO
SUPRelied on87208480USPTO

+8 more marks in this case

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 /v1/proceedings/{id}
ID=prc_2cd841c7-e89e-46c5-91ce-c38e890ae507
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2cd841c7-e89e-46c5-91ce-c38e890ae507",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299309",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-05-29",
  "parties": [
    {
      "name": "Chapter 4 Corp.",
      "role": "opponent"
    },
    {
      "name": "Guangzhou Nanhan Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}