Opposition · USPTO

Opposition 91308260

OtherUSPTO

Opposition 91308260 at USPTO between Duke University and Lmao LLC, over the mark SMOKEY DUKES, filed Jun 22, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 22, 2026
Marks involved
34
Parties

Who is involved

The parties as named in the office record.

Opponent

Duke University

Company trademarks
Respondent

Lmao LLC

Timeline

How the case has moved

Dates from the USPTO record and the SMOKEY DUKES filing.

  1. SMOKEY DUKES filed

    Application 99091252 filed at the USPTO.
  2. Opposition filed

    Duke University started opposition 91308260 at USPTO against SMOKEY DUKES.
Marks

Marks involved

2 contested marks, 32 marks the challenger relies on.

MarkRoleApplicationOffice
SMOKEY DUKESContested99091252USPTO
SMOKEY DUKES LMAO, LLCContested99091259USPTO
DUKE UNIVERSITY STORESRelied on74208327USPTO
DUKE UNIVERSITYRelied on74208934USPTO
DUKE UNIVERSITYRelied on74208935USPTO
DKERelied on74693793USPTO
DKERelied on74694684USPTO
DUKE CENTER FOR LIVINGRelied on75321843USPTO
DUKERelied on75347293USPTO
DUKERelied on75567914USPTO
DUKECARDRelied on75892149USPTO
D KERelied on75976140USPTO

+22 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_41a22762-0c5d-42a1-b5e0-5759ab2c1879
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_41a22762-0c5d-42a1-b5e0-5759ab2c1879",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91308260",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-06-22",
  "parties": [
    {
      "name": "Duke University",
      "role": "opponent"
    },
    {
      "name": "LMAO LLC",
      "role": "respondent"
    }
  ]
}