Opposition · USPTO

Opposition 91304118

PendingUSPTO

Opposition 91304118 at USPTO between LFP IP, LLC and Branded Strategic Hospitality, LLC, over the mark THE HOSPITALITY HUSTLERS, filed Dec 29, 2025. Status in the office record: pending.

Status
Pending
Filed
Dec 29, 2025
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

LFP IP, LLC

Company trademarks
Respondent

Branded Strategic Hospitality, LLC

Timeline

How the case has moved

Dates from the USPTO record and the THE HOSPITALITY HUSTLERS filing.

  1. THE HOSPITALITY HUSTLERS filed

    Application 99171861 filed at the USPTO.
  2. Opposition filed

    LFP IP, LLC started opposition 91304118 at USPTO against THE HOSPITALITY HUSTLERS.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
THE HOSPITALITY HUSTLERSContested99171861USPTO
HUSTLERRelied on76146601USPTO
HUSTLER'S TABOORelied on76326707USPTO
HUSTLER CLUBRelied on76460615USPTO
HUSTLERCASHRelied on85242831USPTO
HUSTLER HOLLYWOODRelied on85681790USPTO
HUSTLER'S FORBIDDENRelied on87164381USPTO
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_149b36ec-849b-415d-af7e-cd5f831475bd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_149b36ec-849b-415d-af7e-cd5f831475bd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91304118",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-12-29",
  "parties": [
    {
      "name": "LFP IP, LLC",
      "role": "opponent"
    },
    {
      "name": "Branded Strategic Hospitality, LLC",
      "role": "respondent"
    }
  ]
}