Opposition · USPTO

Opposition 91293265

OtherUSPTO

Opposition 91293265 at USPTO between Monster Energy Company and Amaidi Universe, LLC, over the mark [Design Mark], filed Aug 13, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 13, 2024
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Monster Energy Company

Company trademarks
Respondent

Amaidi Universe, LLC

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 98147185 filed at the USPTO.
  2. Opposition filed

    Monster Energy Company started opposition 91293265 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested98147185USPTO
MRelied on77274643USPTO
MRelied on77274662USPTO
M MONSTER ENERGYRelied on77705822USPTO
MRelied on78246564USPTO
MRelied on85094362USPTO
MRelied on85094364USPTO
MRelied on86048362USPTO
MRelied on86300585USPTO
M MONSTER ARMYRelied on86906378USPTO
MRelied on87926413USPTO
M MONSTER ENERGYRelied on87926415USPTO

+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_ea83ae1c-50e6-4840-8836-88e9befd9233
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ea83ae1c-50e6-4840-8836-88e9befd9233",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91293265",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-08-13",
  "parties": [
    {
      "name": "Monster Energy Company",
      "role": "opponent"
    },
    {
      "name": "Amaidi Universe, LLC",
      "role": "respondent"
    }
  ]
}