Opposition 91229849
OtherUSPTO
Opposition 91229849 at USPTO between QS Wholesale, Inc. and Roxy Display Inc, over the mark ROXY DISPLAY, filed Aug 31, 2016. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 31, 2016
- Marks involved
- 26
Parties
Who is involved
The parties as named in the office record.
Respondent
Roxy Display Inc
Timeline
How the case has moved
Dates from the USPTO record and the ROXY DISPLAY filing.
ROXY DISPLAY filed
Application 86823742 filed at the USPTO.Opposition filed
QS Wholesale, Inc. started opposition 91229849 at USPTO against ROXY DISPLAY.
Marks
Marks involved
1 contested mark, 25 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| ROXY DISPLAY | Contested | 86823742 | USPTO |
| QUIKSILVER ROXY | Relied on | 75083964 | USPTO |
| ROXY | Relied on | 75408138 | USPTO |
| ROXY | Relied on | 75466979 | USPTO |
| ROXY | Relied on | 75466980 | USPTO |
| ROXY | Relied on | 75473320 | USPTO |
| ROXY | Relied on | 75612754 | USPTO |
| ROXY.COM | Relied on | 75826324 | USPTO |
| ROXY | Relied on | 75826848 | USPTO |
| ROXY | Relied on | 75829696 | USPTO |
| ROXY | Relied on | 75838044 | USPTO |
| QUIKSILVER ROXY | Relied on | 76071940 | USPTO |
+14 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_7ef16eab-db82-4b8e-87e8-9894c95fb109
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_7ef16eab-db82-4b8e-87e8-9894c95fb109",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91229849",
"status": "other",
"office_code": "US",
"filed_date": "2016-08-31",
"parties": [
{
"name": "QS Wholesale, Inc.",
"role": "opponent"
},
{
"name": "Roxy Display Inc",
"role": "respondent"
}
]
}