Opposition · USPTO

Opposition 91305098

OtherUSPTO

Opposition 91305098 at USPTO between Slayer Forever, LLC and Oracle Ltd., over the mark ELBBUB, filed Feb 6, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 6, 2026
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Slayer Forever, LLC

Respondent

Oracle Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ELBBUB filing.

  1. ELBBUB filed

    Application 99259094 filed at the USPTO.
  2. Opposition filed

    Slayer Forever, LLC started opposition 91305098 at USPTO against ELBBUB.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
ELBBUBContested99259094USPTO
BUBS NATURALSRelied on87439568USPTO
BUBS BREWRelied on88716970USPTO
BUBS NATURALS HYDRATE OR DIERelied on88810953USPTO
BUBS NATURALSRelied on90201394USPTO
BUBS NATURALSRelied on90208126USPTO
BUBS NATURALSRelied on97147138USPTO
BUBS NATURALSRelied on97147490USPTO
BUBS NATURALSRelied on97147493USPTO
BUBS BREWRelied on97932340USPTO
BUBS BOOSTRelied on98397612USPTO
BUBS FOUNTAIN OF YOUTHRelied on98905786USPTO

+3 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_1cb185ed-0d1c-4ab7-8f71-8ea14fd64340
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1cb185ed-0d1c-4ab7-8f71-8ea14fd64340",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91305098",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-02-06",
  "parties": [
    {
      "name": "Slayer Forever, LLC",
      "role": "opponent"
    },
    {
      "name": "Oracle Ltd.",
      "role": "respondent"
    }
  ]
}