Opposition · USPTO

Opposition 91292090

OtherUSPTO

Opposition 91292090 at USPTO between Monster Energy Company and BD3, Inc., over the mark M, filed Jun 14, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 14, 2024
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

Monster Energy Company

Company trademarks
Respondent

BD3, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the M filing.

  1. M filed

    Application 98149375 filed at the USPTO.
  2. Opposition filed

    Monster Energy Company started opposition 91292090 at USPTO against M.
Marks

Marks involved

1 contested mark, 23 marks the challenger relies on.

MarkRoleApplicationOffice
MContested98149375USPTO
MRelied on77274643USPTO
MRelied on77274662USPTO
M IMPORTRelied on77800060USPTO
MRelied on78246564USPTO
M MONSTER ENERGYRelied on78246567USPTO
MRelied on86300585USPTO
M MONSTER ENERGY LO-CARBRelied on86521200USPTO
M MONSTER REHABRelied on86521214USPTO
M MONSTER ENERGY ULTRA BLUERelied on86521930USPTO
M MONSTER ENERGY ULTRA REDRelied on86521935USPTO
M MONSTER ENERGY ULTRA SUNRISERelied on86521942USPTO

+12 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_f31e5255-eb5b-4b50-924f-aaedb670d130
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f31e5255-eb5b-4b50-924f-aaedb670d130",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292090",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-06-14",
  "parties": [
    {
      "name": "Monster Energy Company",
      "role": "opponent"
    },
    {
      "name": "BD3, Inc.",
      "role": "respondent"
    }
  ]
}