Opposition 91256299
OtherUSPTO
Opposition 91256299 at USPTO between Uber Technologies, Inc. and Charles Tapley, over the mark LUBER, filed Jun 10, 2020. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jun 10, 2020
- Marks involved
- 29
Parties
Who is involved
The parties as named in the office record.
Respondent
Charles Tapley
Timeline
How the case has moved
Dates from the USPTO record and the LUBER filing.
LUBER filed
Application 88609926 filed at the USPTO.Opposition filed
Uber Technologies, Inc. started opposition 91256299 at USPTO against LUBER.
Marks
Marks involved
1 contested mark, 28 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| LUBER | Contested | 88609926 | USPTO |
| UBER | Relied on | 85170655 | USPTO |
| UBERX | Relied on | 86198791 | USPTO |
| UBERRUSH | Relied on | 86250398 | USPTO |
| UBER EATS | Relied on | 86541663 | USPTO |
| UBERPOOL | Relied on | 86645284 | USPTO |
| UBERPOOL | Relied on | 86984102 | USPTO |
| UBER FREIGHT | Relied on | 87195689 | USPTO |
| UBER ELEVATE | Relied on | 87217185 | USPTO |
| UBER | Relied on | 87256010 | USPTO |
| UBER AIR | Relied on | 87430754 | USPTO |
| UBER HEALTH | Relied on | 87445745 | USPTO |
+17 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_148c722f-3bac-42d5-ae10-f09d39d72a72
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_148c722f-3bac-42d5-ae10-f09d39d72a72",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91256299",
"status": "other",
"office_code": "US",
"filed_date": "2020-06-10",
"parties": [
{
"name": "Uber Technologies, Inc.",
"role": "opponent"
},
{
"name": "Charles Tapley",
"role": "respondent"
}
]
}