Opposition · USPTO

Opposition 91269218

OtherUSPTO

Opposition 91269218 at USPTO between Enterprise Holdings, Inc. and ESW Racing LLC, over the mark E, filed May 10, 2021. Status in the office record: other.

View EGet this data via the API
Status
Other
Result
Other
Filed
May 10, 2021
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Enterprise Holdings, Inc.

Company trademarks
Respondent

ESW Racing LLC

Timeline

How the case has moved

Dates from the USPTO record and the E filing.

  1. E filed

    Application 88956640 filed at the USPTO.

  2. Opposition filed

    Enterprise Holdings, Inc. started opposition 91269218 at USPTO against E.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
EContested88956640USPTO
ERelied on72354153USPTO
ENTERPRISERelied on73346546USPTO
ERelied on74101749USPTO
ENTERPRISERelied on77070178USPTO
ENTERPRISERelied on77070181USPTO
ERelied on77789321USPTO
ENTERPRISERelied on78958771USPTO
ENTERPRISERelied on85675437USPTO
ENTERPRISERelied on85770529USPTO
ERelied on86067298USPTO
ERelied on86067306USPTO

+2 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_4dd49afb-f489-4b69-a339-dd34943734aa
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4dd49afb-f489-4b69-a339-dd34943734aa",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91269218",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-05-10",
  "parties": [
    {
      "name": "Enterprise Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "ESW Racing LLC",
      "role": "respondent"
    }
  ]
}