Opposition · USPTO

Opposition 91284216

OtherUSPTO

Opposition 91284216 at USPTO between Electric Visual Evolution, LLC and Eclektrik Enterprises LLC, over the mark ECLEKTRIK, filed Mar 30, 2023. Status in the office record: other.

View ECLEKTRIKGet this data via the API
Status
Other
Result
Other
Filed
Mar 30, 2023
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Electric Visual Evolution, LLC

Company trademarks
Respondent

Eclektrik Enterprises LLC

Timeline

How the case has moved

Dates from the USPTO record and the ECLEKTRIK filing.

  1. ECLEKTRIK filed

    Application 97330178 filed at the USPTO.

  2. Opposition filed

    Electric Visual Evolution, LLC started opposition 91284216 at USPTO against ECLEKTRIK.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
ECLEKTRIKContested97330178USPTO
ELECTRICRelied on75932154USPTO
ELECTRICRelied on75932155USPTO
ELECTRICRelied on75932156USPTO
ELECTRICRelied on75936417USPTO
ELECTRICRelied on75983559USPTO
ELECTRIC VISUALRelied on77213653USPTO
ELECTRICRelied on85876719USPTO
ELECTRICRelied on85876742USPTO
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_28e77d43-385b-4d38-8883-55df18659f7e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_28e77d43-385b-4d38-8883-55df18659f7e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284216",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-03-30",
  "parties": [
    {
      "name": "Electric Visual Evolution, LLC",
      "role": "opponent"
    },
    {
      "name": "Eclektrik Enterprises LLC",
      "role": "respondent"
    }
  ]
}