Opposition · USPTO

Opposition 91281941

OtherUSPTO

Opposition 91281941 at USPTO between Monster Energy Company and Truthful Trading Inc, over the mark BEARCLAW, filed Nov 22, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 22, 2022
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Monster Energy Company

Company trademarks
Respondent

Truthful Trading Inc

Timeline

How the case has moved

Dates from the USPTO record and the BEARCLAW filing.

  1. BEARCLAW filed

    Application 97013538 filed at the USPTO.
  2. Opposition filed

    Monster Energy Company started opposition 91281941 at USPTO against BEARCLAW.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
BEARCLAWContested97013538USPTO
MRelied on77274662USPTO
M MONSTER ENERGYRelied on77705747USPTO
M MONSTER ENERGYRelied on77705822USPTO
MRelied on78246564USPTO
M MONSTER ENERGYRelied on78246567USPTO
MRelied on85094343USPTO
MRelied on85094362USPTO
MRelied on86300585USPTO
M MONSTER ENERGYRelied on87707552USPTO
MRelied on87926413USPTO
M MONSTER ENERGYRelied on87926415USPTO

+1 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_e92569e1-813e-4e48-8423-936dd5a513c7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e92569e1-813e-4e48-8423-936dd5a513c7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91281941",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-11-22",
  "parties": [
    {
      "name": "Monster Energy Company",
      "role": "opponent"
    },
    {
      "name": "Truthful Trading Inc",
      "role": "respondent"
    }
  ]
}