Opposition · USPTO

Opposition 91240657

OtherUSPTO

Opposition 91240657 at USPTO between LFP IP, LLC and MR Property Buyer, over the mark SAVAGE HUSTLERS, filed Apr 12, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 12, 2018
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

LFP IP, LLC

Company trademarks
Respondent

MR Property Buyer

Timeline

How the case has moved

Dates from the USPTO record and the SAVAGE HUSTLERS filing.

  1. SAVAGE HUSTLERS filed

    Application 87577268 filed at the USPTO.
  2. Opposition filed

    LFP IP, LLC started opposition 91240657 at USPTO against SAVAGE HUSTLERS.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
SAVAGE HUSTLERSContested87577268USPTO
HUSTLERRelied on73020748USPTO
HUSTLERRelied on75180097USPTO
HUSTLERRelied on75321822USPTO
HUSTLER HOLLYWOODRelied on75524462USPTO
HUSTLERRelied on75982556USPTO
HUSTLERRelied on76146601USPTO
HUSTLER CLUBRelied on76460615USPTO
HUSTLERRelied on77229341USPTO
HUSTLERRelied on78688221USPTO
HUSTLER HOLLYWOODRelied on85681790USPTO
HUSTLERRelied on85762250USPTO

+2 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_036395ed-f62f-4b9b-b8b9-45851c96e3dd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_036395ed-f62f-4b9b-b8b9-45851c96e3dd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91240657",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-04-12",
  "parties": [
    {
      "name": "LFP IP, LLC",
      "role": "opponent"
    },
    {
      "name": "MR Property Buyer",
      "role": "respondent"
    }
  ]
}