Opposition · USPTO

Opposition 91311146

PendingUSPTO

Opposition 91311146 at USPTO between Chapter 4 Corp. and Nar Darmanko LLC, over the mark SUPR ME, filed Oct 14, 2026. Status in the office record: pending.

Status
Pending
Filed
Oct 14, 2026
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Chapter 4 Corp.

Respondent

Nar Darmanko LLC

Timeline

How the case has moved

Dates from the USPTO record and the SUPR ME filing.

  1. SUPR ME filed

    Application 99704227 filed at the USPTO.
  2. Opposition filed

    Chapter 4 Corp. started opposition 91311146 at USPTO against SUPR ME.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
SUPR MEContested99704227USPTO
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_17b21939-35b7-4d1e-a4aa-4bee522ec6e2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_17b21939-35b7-4d1e-a4aa-4bee522ec6e2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91311146",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-10-14",
  "parties": [
    {
      "name": "Chapter 4 Corp.",
      "role": "opponent"
    },
    {
      "name": "NAR DARMANKO LLC",
      "role": "respondent"
    }
  ]
}