Opposition 91250593
OtherUSPTO
Opposition 91250593 at USPTO between Bear USA, Inc. and Sean Mitchell, over the mark TOXYBEAR, filed Sep 3, 2019. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Sep 3, 2019
- Marks involved
- 13
Parties
Who is involved
The parties as named in the office record.
Opponent
Bear USA, Inc.
Respondent
Sean Mitchell
Timeline
How the case has moved
Dates from the USPTO record and the TOXYBEAR filing.
TOXYBEAR filed
Application 88333340 filed at the USPTO.Opposition filed
Bear USA, Inc. started opposition 91250593 at USPTO against TOXYBEAR.
Marks
Marks involved
1 contested mark, 12 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| TOXYBEAR | Contested | 88333340 | USPTO |
| BEAR | Relied on | 74625218 | USPTO |
| BEAR | Relied on | 74625219 | USPTO |
| BEAR U.S.A., INC. | Relied on | 74802359 | USPTO |
| BEAR | Relied on | 75063344 | USPTO |
| BEAR | Relied on | 75063345 | USPTO |
| BEAR USA | Relied on | 75371191 | USPTO |
| BABY BEAR | Relied on | 75463798 | USPTO |
| BABY BEAR | Relied on | 75463799 | USPTO |
| BEAR MOUNTAIN | Relied on | 75472696 | USPTO |
| BABY BEAR | Relied on | 75978499 | USPTO |
| BEAR USA | Relied on | 75983105 | USPTO |
+1 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_5d4beed7-1dad-4942-a51a-c7b27dc138e4
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_5d4beed7-1dad-4942-a51a-c7b27dc138e4",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91250593",
"status": "other",
"office_code": "US",
"filed_date": "2019-09-03",
"parties": [
{
"name": "Bear USA, Inc.",
"role": "opponent"
},
{
"name": "Sean Mitchell",
"role": "respondent"
}
]
}