Opposition 91296647
OtherUSPTO
Opposition 91296647 at USPTO between Fca Us LLC and Shenzhen Kui'ente Technology Co., Ltd., over the mark GEEPFINE, filed Jan 31, 2025. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 31, 2025
- Marks involved
- 28
Parties
Who is involved
The parties as named in the office record.
Respondent
Shenzhen Kui'ente Technology Co., Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the GEEPFINE filing.
GEEPFINE filed
Application 98426522 filed at the USPTO.Opposition filed
Fca Us LLC started opposition 91296647 at USPTO against GEEPFINE.
Marks
Marks involved
1 contested mark, 27 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| GEEPFINE | Contested | 98426522 | USPTO |
| JEEP | Relied on | 71458520 | USPTO |
| JEEP | Relied on | 73087711 | USPTO |
| JEEP | Relied on | 73179481 | USPTO |
| JEEP | Relied on | 73179494 | USPTO |
| JEEP | Relied on | 73179676 | USPTO |
| JEEP | Relied on | 73180458 | USPTO |
| JEEP | Relied on | 73180533 | USPTO |
| JEEP | Relied on | 73371202 | USPTO |
| JEEP | Relied on | 75529121 | USPTO |
| JEEP | Relied on | 75529123 | USPTO |
| JEEP 101 | Relied on | 75724370 | USPTO |
+16 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_d2b40a63-0c09-4c4f-b77e-c8aaad5dcb47
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_d2b40a63-0c09-4c4f-b77e-c8aaad5dcb47",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91296647",
"status": "other",
"office_code": "US",
"filed_date": "2025-01-31",
"parties": [
{
"name": "FCA US LLC",
"role": "opponent"
},
{
"name": "Shenzhen Kui'ente Technology Co., Ltd.",
"role": "respondent"
}
]
}