Opposition · USPTO

Opposition 91287309

OtherUSPTO

Opposition 91287309 at USPTO between Monster Energy Company and Noah Foster, over the mark MSTERLAW, filed Sep 22, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 22, 2023
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Monster Energy Company

Company trademarks
Respondent

Noah Foster

Timeline

How the case has moved

Dates from the USPTO record and the MSTERLAW filing.

  1. MSTERLAW filed

    Application 97572298 filed at the USPTO.
  2. Opposition filed

    Monster Energy Company started opposition 91287309 at USPTO against MSTERLAW.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
MSTERLAWContested97572298USPTO
MRelied on77274662USPTO
M MONSTER ENERGYRelied on77705747USPTO
MRelied on78246564USPTO
M MONSTER ENERGYRelied on78246567USPTO
MRelied on85094343USPTO
M MONSTER ENERGYRelied on85747244USPTO
M MONSTER ENERGYRelied on86048359USPTO
MONSTER ENERGYRelied on87208532USPTO
MONSTERRelied on87719840USPTO
MRelied on87926413USPTO
M MONSTER ENERGYRelied on87926415USPTO

+2 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_8c12eb9c-0099-4a1b-b31f-a0cd356253f8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8c12eb9c-0099-4a1b-b31f-a0cd356253f8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91287309",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-09-22",
  "parties": [
    {
      "name": "Monster Energy Company",
      "role": "opponent"
    },
    {
      "name": "Noah Foster",
      "role": "respondent"
    }
  ]
}