Opposition 91287944
OtherUSPTO
Opposition 91287944 at USPTO between Ridestore Holding AB and Quazar LLC, over the mark PLAY DOPE, filed Oct 30, 2023. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Oct 30, 2023
- Marks involved
- 14
Parties
Who is involved
The parties as named in the office record.
Opponent
Ridestore Holding AB
Respondent
Quazar LLC
Timeline
How the case has moved
Dates from the USPTO record and the PLAY DOPE filing.
PLAY DOPE filed
Application 97674784 filed at the USPTO.Opposition filed
Ridestore Holding AB started opposition 91287944 at USPTO against PLAY DOPE.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| PLAY DOPE | Contested | 97674784 | USPTO |
| DOPE | Relied on | 79300325 | USPTO |
| DOPE | Relied on | 85375315 | USPTO |
| DOPE | Relied on | 85841683 | USPTO |
| DOPEST | Relied on | 85930325 | USPTO |
| DOPE | Relied on | 86293042 | USPTO |
| DOPE SPORT | Relied on | 87222632 | USPTO |
| DOPE DENIM | Relied on | 87222671 | USPTO |
| DOPE | Relied on | 88000969 | USPTO |
| DOPE COUTURE | Relied on | 90333319 | USPTO |
| DOPE | Relied on | 90333343 | USPTO |
| DOPE | Relied on | 90333365 | USPTO |
+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_d09f3728-b6b2-49d1-a0c4-6488aa62ac04
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_d09f3728-b6b2-49d1-a0c4-6488aa62ac04",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91287944",
"status": "other",
"office_code": "US",
"filed_date": "2023-10-30",
"parties": [
{
"name": "Ridestore Holding AB",
"role": "opponent"
},
{
"name": "Quazar LLC",
"role": "respondent"
}
]
}