Opposition · USPTO

Opposition 91264448

OtherUSPTO

Opposition 91264448 at USPTO between Uber Technologies, Inc. and Uberdjs LLC, over the mark THEUBERDJS, filed Aug 26, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 26, 2020
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Company trademarks
Respondent

Uberdjs LLC

Timeline

How the case has moved

Dates from the USPTO record and the THEUBERDJS filing.

  1. THEUBERDJS filed

    Application 88739597 filed at the USPTO.
  2. Opposition filed

    Uber Technologies, Inc. started opposition 91264448 at USPTO against THEUBERDJS.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
THEUBERDJSContested88739597USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBERRUSHRelied on86250398USPTO
UBER EATSRelied on86541663USPTO
UBERPOOLRelied on86645284USPTO
UBERPOOLRelied on86984102USPTO
UBER ELEVATERelied on87217185USPTO
UBERRelied on87256010USPTO
UBER AIRRelied on87430754USPTO
UBER PRESENTSRelied on87540897USPTO
UBER AI LABSRelied on87554691USPTO

+6 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_0ade82fc-9997-4810-9d60-3de42aa428ed
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0ade82fc-9997-4810-9d60-3de42aa428ed",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264448",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-08-26",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "UBERDJS LLC",
      "role": "respondent"
    }
  ]
}