Opposition · USPTO

Opposition 91301836

OtherUSPTO

Opposition 91301836 at USPTO between Uber Technologies, Inc. and Uber Smog LLC, over the mark UBERSMOG, filed Sep 19, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 19, 2025
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Company trademarks
Respondent

Uber Smog LLC

Timeline

How the case has moved

Dates from the USPTO record and the UBERSMOG filing.

  1. UBERSMOG filed

    Application 98945456 filed at the USPTO.
  2. Opposition filed

    Uber Technologies, Inc. started opposition 91301836 at USPTO against UBERSMOG.
Marks

Marks involved

1 contested mark, 21 marks the challenger relies on.

MarkRoleApplicationOffice
UBERSMOGContested98945456USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBER HEALTHRelied on86496538USPTO
UBER EATSRelied on86541663USPTO
UBERRelied on87256010USPTO
UBER HEALTHRelied on87445745USPTO
UBER PRESENTSRelied on87540897USPTO
UBER MOVEMENTRelied on87818737USPTO
UBER FREIGHT PLUSRelied on87844357USPTO
UBER RENTRelied on87878896USPTO
UBERRelied on87980887USPTO

+10 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_54c3ee54-dd04-4e67-8e32-30b63040f6dd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_54c3ee54-dd04-4e67-8e32-30b63040f6dd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91301836",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-09-19",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Uber Smog LLC",
      "role": "respondent"
    }
  ]
}