Opposition · USPTO

Opposition 91311157

PendingUSPTO

Opposition 91311157 at USPTO between Entrepreneur Media, LLC and Loya Cosulting Group, LLC; Rami Loya, over the mark ENTREPRENEUR BIBLE, filed Oct 14, 2026. Status in the office record: pending.

Status
Pending
Filed
Oct 14, 2026
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Entrepreneur Media, LLC

Respondent

Loya Cosulting Group, LLC; Rami Loya

Timeline

How the case has moved

Dates from the USPTO record and the ENTREPRENEUR BIBLE filing.

  1. ENTREPRENEUR BIBLE filed

    Application 98931648 filed at the USPTO.
  2. Opposition filed

    Entrepreneur Media, LLC started opposition 91311157 at USPTO against ENTREPRENEUR BIBLE.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
ENTREPRENEUR BIBLEContested98931648USPTO
ENTREPRENEURRelied on73537579USPTO
ENTREPRENEURRelied on75018382USPTO
ENTREPRENEURRelied on76159837USPTO
ENTREPRENEURRelied on85607634USPTO
ENTREPRENEURRelied on85607635USPTO
ENTREPRENEURRelied on86786104USPTO
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_e6b411de-2682-496b-8f1d-ec62f68633a5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e6b411de-2682-496b-8f1d-ec62f68633a5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91311157",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-10-14",
  "parties": [
    {
      "name": "Entrepreneur Media, LLC",
      "role": "opponent"
    },
    {
      "name": "Loya Cosulting Group, LLC; Rami Loya",
      "role": "respondent"
    }
  ]
}