Opposition 91289568
OtherUSPTO
Opposition 91289568 at USPTO between Monster Energy Company and Solo Warrior LLC, over the mark [Design Mark], filed Feb 2, 2024. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Feb 2, 2024
- Marks involved
- 18
Parties
Who is involved
The parties as named in the office record.
Respondent
Solo Warrior LLC
Timeline
How the case has moved
Dates from the USPTO record and the [Design Mark] filing.
[Design Mark] filed
Application 97774339 filed at the USPTO.Opposition filed
Monster Energy Company started opposition 91289568 at USPTO against [Design Mark].
Marks
Marks involved
1 contested mark, 17 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| [Design mark] | Contested | 97774339 | USPTO |
| M | Relied on | 77274643 | USPTO |
| M | Relied on | 77274662 | USPTO |
| M MONSTER ENERGY | Relied on | 77705822 | USPTO |
| M | Relied on | 78246564 | USPTO |
| M MONSTER ENERGY | Relied on | 78246567 | USPTO |
| M | Relied on | 85094362 | USPTO |
| M | Relied on | 85094364 | USPTO |
| M | Relied on | 86048362 | USPTO |
| M | Relied on | 86300585 | USPTO |
| M MONSTER ARMY | Relied on | 86906378 | USPTO |
| M | Relied on | 86979712 | USPTO |
+6 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_548ca941-3c39-40ba-a126-53e2a3aa1c04
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_548ca941-3c39-40ba-a126-53e2a3aa1c04",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91289568",
"status": "other",
"office_code": "US",
"filed_date": "2024-02-02",
"parties": [
{
"name": "Monster Energy Company",
"role": "opponent"
},
{
"name": "Solo Warrior LLC",
"role": "respondent"
}
]
}