Opposition 91286119
OtherUSPTO
Opposition 91286119 at USPTO between Ridestore Holding AB and Louis Ring, over the mark BEEN DOPE, filed Jul 19, 2023. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jul 19, 2023
- Marks involved
- 14
Parties
Who is involved
The parties as named in the office record.
Opponent
Ridestore Holding AB
Respondent
Louis Ring
Timeline
How the case has moved
Dates from the USPTO record and the BEEN DOPE filing.
BEEN DOPE filed
Application 90885059 filed at the USPTO.Opposition filed
Ridestore Holding AB started opposition 91286119 at USPTO against BEEN DOPE.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| BEEN DOPE | Contested | 90885059 | 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_9ba6ddd7-d89b-4269-8e72-7386d6ca4b82
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_9ba6ddd7-d89b-4269-8e72-7386d6ca4b82",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91286119",
"status": "other",
"office_code": "US",
"filed_date": "2023-07-19",
"parties": [
{
"name": "Ridestore Holding AB",
"role": "opponent"
},
{
"name": "Louis Ring",
"role": "respondent"
}
]
}