Opposition 91264503
OtherUSPTO
Opposition 91264503 at USPTO between Enterprise Holdings, Inc. and Rajax Network & Technology (Shanghai) Co., Ltd., over the mark E, filed Aug 31, 2020. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 31, 2020
- Marks involved
- 16
Parties
Who is involved
The parties as named in the office record.
Respondent
Rajax Network & Technology (Shanghai) Co., Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the E filing.
E filed
Application 88693243 filed at the USPTO.Opposition filed
Enterprise Holdings, Inc. started opposition 91264503 at USPTO against E.
Marks
Marks involved
1 contested mark, 15 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| E | Contested | 88693243 | USPTO |
| E | Relied on | 73033536 | USPTO |
| E | Relied on | 74101749 | USPTO |
| E | Relied on | 74465251 | USPTO |
| E | Relied on | 74465260 | USPTO |
| E | Relied on | 75500184 | USPTO |
| E | Relied on | 77681395 | USPTO |
| E | Relied on | 78958766 | USPTO |
| E | Relied on | 85125599 | USPTO |
| E | Relied on | 85125611 | USPTO |
| E | Relied on | 86644510 | USPTO |
| E | Relied on | 86644545 | USPTO |
+4 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_cc77e04c-3108-4833-897d-bc04a729cc89
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_cc77e04c-3108-4833-897d-bc04a729cc89",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91264503",
"status": "other",
"office_code": "US",
"filed_date": "2020-08-31",
"parties": [
{
"name": "Enterprise Holdings, Inc.",
"role": "opponent"
},
{
"name": "Rajax Network & Technology (Shanghai) Co., Ltd.",
"role": "respondent"
}
]
}