Opposition · USPTO

Opposition 91232271

OtherUSPTO

Opposition 91232271 at USPTO between LFP IP, LLC and Paul Ruszkai, over the mark HUSTLERS SPIRIT, filed Jan 13, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 13, 2017
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

LFP IP, LLC

Company trademarks
Respondent

Paul Ruszkai

Timeline

How the case has moved

Dates from the USPTO record and the HUSTLERS SPIRIT filing.

  1. HUSTLERS SPIRIT filed

    Application 87080815 filed at the USPTO.
  2. Opposition filed

    LFP IP, LLC started opposition 91232271 at USPTO against HUSTLERS SPIRIT.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
HUSTLERS SPIRITContested87080815USPTO
HUSTLERRelied on73020748USPTO
HUSTLER HUMORRelied on73203927USPTO
HUSTLER FANTASIESRelied on73491690USPTO
HUSTLERRelied on75180097USPTO
HUSTLERRelied on75982556USPTO
HUSTLERRelied on76146601USPTO
HUSTLER CLUBRelied on76460615USPTO
HUSTLERRelied on77229341USPTO
HUSTLERRelied on78688221USPTO
HUSTLER HOLLYWOODRelied on85681790USPTO
HUSTLERSTORERelied on85681899USPTO

+4 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_eaf1192e-d5b9-4e54-9f65-db2de500eeae
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_eaf1192e-d5b9-4e54-9f65-db2de500eeae",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91232271",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-01-13",
  "parties": [
    {
      "name": "LFP IP, LLC",
      "role": "opponent"
    },
    {
      "name": "Paul Ruszkai",
      "role": "respondent"
    }
  ]
}