Opposition · USPTO

Opposition 91233874

OtherUSPTO

Opposition 91233874 at USPTO between LFP IP, LLC and Clarence Ryans, over the mark BEARDED HUSTLERS, filed Apr 7, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 7, 2017
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

LFP IP, LLC

Company trademarks
Respondent

Clarence Ryans

Timeline

How the case has moved

Dates from the USPTO record and the BEARDED HUSTLERS filing.

  1. BEARDED HUSTLERS filed

    Application 86943491 filed at the USPTO.
  2. Opposition filed

    LFP IP, LLC started opposition 91233874 at USPTO against BEARDED HUSTLERS.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
BEARDED HUSTLERSContested86943491USPTO
HUSTLERRelied on73020748USPTO
HUSTLER HUMORRelied on73203927USPTO
HUSTLER FANTASIESRelied on73491690USPTO
HUSTLERRelied on75180097USPTO
HUSTLERRelied on75321822USPTO
HUSTLER HOLLYWOODRelied on75524462USPTO
HUSTLERRelied on75982556USPTO
HUSTLERRelied on76146601USPTO
HUSTLER CLUBRelied on76460615USPTO
HUSTLERRelied on77229341USPTO
HUSTLERRelied on78688221USPTO

+5 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_cddcf136-6178-485c-8484-df91d504658a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_cddcf136-6178-485c-8484-df91d504658a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91233874",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-04-07",
  "parties": [
    {
      "name": "LFP IP, LLC",
      "role": "opponent"
    },
    {
      "name": "Clarence Ryans",
      "role": "respondent"
    }
  ]
}