Cancellation · USPTO

Cancellation 92081414

OtherUSPTO

Cancellation 92081414 at USPTO between Play Like A Champion Today, LLC and HBI Branded Apparel Enterprises, LLC, over the mark PLAY LIKE A CHAMPION, filed Jan 23, 2023. Status in the office record: other.

View PLAY LIKE A CHAMPIONGet this data via the API
Status
Other
Result
Other
Filed
Jan 23, 2023
Marks involved
3
Parties

Who is involved

The parties as named in the office record.

Petitioner

Play Like A Champion Today, LLC

Respondent

HBI Branded Apparel Enterprises, LLC

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the PLAY LIKE A CHAMPION filing.

  1. PLAY LIKE A CHAMPION filed

    Application 87097010 filed at the USPTO.

  2. PLAY LIKE A CHAMPION registered

  3. Cancellation filed

    Play Like A Champion Today, LLC started cancellation 92081414 at USPTO against PLAY LIKE A CHAMPION.
Marks

Marks involved

1 contested mark, 2 marks the challenger relies on.

MarkRoleApplicationOffice
PLAY LIKE A CHAMPIONContested87097010USPTO
PLAY LIKE A CHAMPION TODAYRelied on78948106USPTO
PLAY LIKE A CHAMPION TODAYRelied on90245184USPTO
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_0ff678f6-c97e-4ede-a2b6-f0537cee49d2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0ff678f6-c97e-4ede-a2b6-f0537cee49d2",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92081414",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-01-23",
  "parties": [
    {
      "name": "Play Like A Champion Today, LLC",
      "role": "petitioner"
    },
    {
      "name": "HBI Branded Apparel Enterprises, LLC",
      "role": "respondent"
    }
  ]
}