Opposition 91286009
OtherUSPTO
Opposition 91286009 at USPTO between Chapter 4 Corp. and Jiaozuo Nanyu Trading Co.,Ltd., over the mark SUPREDOG, filed Jul 12, 2023. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jul 12, 2023
- Marks involved
- 20
Parties
Who is involved
The parties as named in the office record.
Opponent
Chapter 4 Corp.
Timeline
How the case has moved
Dates from the USPTO record and the SUPREDOG filing.
SUPREDOG filed
Application 97515395 filed at the USPTO.Opposition filed
Chapter 4 Corp. started opposition 91286009 at USPTO against SUPREDOG.
Marks
Marks involved
1 contested mark, 19 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| SUPREDOG | Contested | 97515395 | USPTO |
| SUPREME | Relied on | 85424627 | USPTO |
| SUPREME | Relied on | 85424722 | USPTO |
| SUPREME | Relied on | 85868093 | USPTO |
| SUPREME | Relied on | 85868116 | USPTO |
| SUPREME | Relied on | 86225786 | USPTO |
| SUPREME | Relied on | 86225846 | USPTO |
| SUPREME | Relied on | 86225879 | USPTO |
| SUPREME | Relied on | 86225910 | USPTO |
| SUPREME | Relied on | 86691471 | USPTO |
| SUPREME | Relied on | 86691492 | USPTO |
| SUP | Relied on | 87208480 | USPTO |
+8 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_b49462b8-65e2-49ec-91f6-a258ac7301ab
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_b49462b8-65e2-49ec-91f6-a258ac7301ab",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91286009",
"status": "other",
"office_code": "US",
"filed_date": "2023-07-12",
"parties": [
{
"name": "Chapter 4 Corp.",
"role": "opponent"
},
{
"name": "Jiaozuo Nanyu Trading Co.,Ltd.",
"role": "respondent"
}
]
}