Opposition 91297049
OtherUSPTO
Opposition 91297049 at USPTO between Uber Technologies, Inc. and Uberhot SpA, over the mark UBERHOT, filed Feb 18, 2025. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Feb 18, 2025
- Marks involved
- 28
Parties
Who is involved
The parties as named in the office record.
Respondent
Uberhot SpA
Timeline
How the case has moved
Dates from the USPTO record and the UBERHOT filing.
UBERHOT filed
Application 97115677 filed at the USPTO.Opposition filed
Uber Technologies, Inc. started opposition 91297049 at USPTO against UBERHOT.
Marks
Marks involved
1 contested mark, 27 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| UBERHOT | Contested | 97115677 | USPTO |
| UBER | Relied on | 85170655 | USPTO |
| UBERX | Relied on | 86198791 | USPTO |
| UBER HEALTH | Relied on | 86496538 | USPTO |
| UBER EATS | Relied on | 86541663 | USPTO |
| UBERPOOL | Relied on | 86645284 | USPTO |
| UBERPOOL | Relied on | 86984102 | USPTO |
| UBER ELEVATE | Relied on | 87217185 | USPTO |
| UBER | Relied on | 87256010 | USPTO |
| UBER AIR | Relied on | 87430754 | USPTO |
| UBER HEALTH | Relied on | 87445745 | USPTO |
| UBER PRESENTS | Relied on | 87540897 | 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_8459ef30-8bb9-449d-9ea7-64b9ddb0043e
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_8459ef30-8bb9-449d-9ea7-64b9ddb0043e",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91297049",
"status": "other",
"office_code": "US",
"filed_date": "2025-02-18",
"parties": [
{
"name": "Uber Technologies, Inc.",
"role": "opponent"
},
{
"name": "Uberhot SpA",
"role": "respondent"
}
]
}