Opposition 91243320
OtherUSPTO
Opposition 91243320 at USPTO between Uber Technologies, Inc. and Valenco Corporation, over the mark UBERLAND, filed Aug 29, 2018. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 29, 2018
- Marks involved
- 12
Parties
Who is involved
The parties as named in the office record.
Respondent
Valenco Corporation
Timeline
How the case has moved
Dates from the USPTO record and the UBERLAND filing.
UBERLAND filed
Application 87501759 filed at the USPTO.Opposition filed
Uber Technologies, Inc. started opposition 91243320 at USPTO against UBERLAND.
Marks
Marks involved
1 contested mark, 11 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| UBERLAND | Contested | 87501759 | 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 |
| UBERCOMMUTE | Relied on | 86765078 | 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 |
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_7a599e13-6f1f-4edb-96e7-a8f4f4318ac3
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_7a599e13-6f1f-4edb-96e7-a8f4f4318ac3",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91243320",
"status": "other",
"office_code": "US",
"filed_date": "2018-08-29",
"parties": [
{
"name": "Uber Technologies, Inc.",
"role": "opponent"
},
{
"name": "Valenco Corporation",
"role": "respondent"
}
]
}