Opposition · USPTO

Opposition 91299828

SuspendedUSPTO

Opposition 91299828 at USPTO between Uberlube. Inc. and Ultra Badass Eco Lubricants LLC AKA UBELUBE, over the mark UBELUBE BOROGRAPHENE, filed Jun 19, 2025. Status in the office record: suspended.

View UBELUBE BOROGRAPHENEGet this data via the API
Status
Suspended
Filed
Jun 19, 2025
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Uberlube. Inc.

Respondent

Ultra Badass Eco Lubricants LLC AKA UBELUBE

Timeline

How the case has moved

Dates from the USPTO record and the UBELUBE BOROGRAPHENE filing.

  1. UBELUBE BOROGRAPHENE filed

    Application 98204122 filed at the USPTO.

  2. Opposition filed

    Uberlube. Inc. started opposition 91299828 at USPTO against UBELUBE BOROGRAPHENE.
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

2 contested marks, 4 marks the challenger relies on.

MarkRoleApplicationOffice
UBELUBE BOROGRAPHENEContested98204122USPTO
UBELUBEContested98586508USPTO
UBERLUBERelied on86881396USPTO
ÜRelied on86881411USPTO
ÜRelied on97453501USPTO
UBERLUBERelied on97453526USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_b926ba24-0b93-4b43-9e2e-cd814584467d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b926ba24-0b93-4b43-9e2e-cd814584467d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299828",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2025-06-19",
  "parties": [
    {
      "name": "Uberlube. Inc.",
      "role": "opponent"
    },
    {
      "name": "Ultra Badass Eco Lubricants LLC AKA UBELUBE",
      "role": "respondent"
    }
  ]
}