Opposition · USPTO

Opposition 91305319

OtherUSPTO

Opposition 91305319 at USPTO between Duke University and Michelle Dukes, over the mark DUKE & DUKES LEGACY, filed Feb 18, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 18, 2026
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Duke University

Company trademarks
Respondent

Michelle Dukes

Timeline

How the case has moved

Dates from the USPTO record and the DUKE & DUKES LEGACY filing.

  1. DUKE & DUKES LEGACY filed

    Application 98951860 filed at the USPTO.
  2. Opposition filed

    Duke University started opposition 91305319 at USPTO against DUKE & DUKES LEGACY.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
DUKE & DUKES LEGACYContested98951860USPTO
DUKE UNIVERSITYRelied on74208934USPTO
DUKE UNIVERSITYRelied on74208935USPTO
DKERelied on74693793USPTO
DKERelied on74694684USPTO
DUKERelied on75347293USPTO
DUKERelied on75567914USPTO
D KERelied on75976140USPTO
DKERelied on75976141USPTO
DUKERelied on78944306USPTO
DUKERelied on78944344USPTO
IRON DUKESRelied on85356737USPTO

+7 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_7415a907-47ab-4da8-abc0-201240f26b49
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7415a907-47ab-4da8-abc0-201240f26b49",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91305319",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-02-18",
  "parties": [
    {
      "name": "Duke University",
      "role": "opponent"
    },
    {
      "name": "Michelle Dukes",
      "role": "respondent"
    }
  ]
}