Opposition · USPTO

Opposition 91295262

OtherUSPTO

Opposition 91295262 at USPTO between Hugo Boss AG and Meyer Lucas Media LLC, over the mark HYPE BOSS, filed Nov 20, 2024. Status in the office record: other.

View HYPE BOSSGet this data via the API
Status
Other
Result
Other
Filed
Nov 20, 2024
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

Hugo Boss AG

Respondent

Meyer Lucas Media LLC

Timeline

How the case has moved

Dates from the USPTO record and the HYPE BOSS filing.

  1. HYPE BOSS filed

    Application 98256262 filed at the USPTO.

  2. Opposition filed

    Hugo Boss AG started opposition 91295262 at USPTO against HYPE BOSS.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
HYPE BOSSContested98256262USPTO
BOSSRelied on73036140USPTO
BOSSRelied on73569217USPTO
BOSSRelied on73665340USPTO
BOSSRelied on73665341USPTO
HUGO BOSSRelied on73665342USPTO
BOSSRelied on73665343USPTO
HUGO BOSSRelied on73665364USPTO
BOSS HUGO BOSSRelied on73665965USPTO
BOSS HUGO BOSSRelied on73747911USPTO
BOSSRelied on74074962USPTO
BOSSRelied on74075953USPTO

+38 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_1303d81d-3cb1-4113-bc3b-5cd204dd146b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1303d81d-3cb1-4113-bc3b-5cd204dd146b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91295262",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-11-20",
  "parties": [
    {
      "name": "Hugo Boss AG",
      "role": "opponent"
    },
    {
      "name": "Meyer Lucas Media LLC",
      "role": "respondent"
    }
  ]
}