Opposition · USPTO

Opposition 91241678

OtherUSPTO

Opposition 91241678 at USPTO between Starz Entertainment, LLC and Estarz, Inc., over the mark ESTARZ, filed Jun 8, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 8, 2018
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Starz Entertainment, LLC

Company trademarks
Respondent

Estarz, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the ESTARZ filing.

  1. ESTARZ filed

    Application 87504983 filed at the USPTO.
  2. Opposition filed

    Starz Entertainment, LLC started opposition 91241678 at USPTO against ESTARZ.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
ESTARZContested87504983USPTO
STARZ!Relied on75046761USPTO
STARZ ON DEMANDRelied on75778994USPTO
STARZ CINEMARelied on76188927USPTO
STARZRelied on77487276USPTO
STARZRelied on77574568USPTO
STARZ! HDRelied on78436564USPTO
STARZ EDGERelied on78502432USPTO
STARZ COMEDYRelied on78502435USPTO
STARZ INBLACKRelied on78502446USPTO
STARZ KIDS & FAMILYRelied on78503295USPTO
STARZRelied on78559871USPTO

+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 /v1/proceedings/{id}
ID=prc_307fe2fb-f93a-477d-b84a-2f1ca406d109
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_307fe2fb-f93a-477d-b84a-2f1ca406d109",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91241678",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-06-08",
  "parties": [
    {
      "name": "Starz Entertainment, LLC",
      "role": "opponent"
    },
    {
      "name": "Estarz, Inc.",
      "role": "respondent"
    }
  ]
}