Opposition · USPTO

Opposition 91276906

OtherUSPTO

Opposition 91276906 at USPTO between NIKE, Inc. and Nike Unlimited Care LLC, over the mark NIKE UNLIMITED CARE LLC, filed Jun 22, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 22, 2022
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

NIKE, Inc.

Company trademarks
Respondent

Nike Unlimited Care LLC

Timeline

How the case has moved

Dates from the USPTO record and the NIKE UNLIMITED CARE LLC filing.

  1. NIKE UNLIMITED CARE LLC filed

    Application 90668161 filed at the USPTO.
  2. Opposition filed

    NIKE, Inc. started opposition 91276906 at USPTO against NIKE UNLIMITED CARE LLC.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
NIKE UNLIMITED CARE LLCContested90668161USPTO
NIKERelied on72414176USPTO
NIKERelied on73200253USPTO
NIKERelied on73302504USPTO
NIKERelied on73302505USPTO
NIKERelied on73361067USPTO
NIKERelied on74384106USPTO
NIKERelied on74605806USPTO
NIKERelied on74612654USPTO
NIKERelied on74624334USPTO
NIKERelied on75977720USPTO
NIKERelied on78411705USPTO

+5 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_7bb78c1a-cac2-4e03-b380-4ec7e1ecf2a8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7bb78c1a-cac2-4e03-b380-4ec7e1ecf2a8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91276906",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-06-22",
  "parties": [
    {
      "name": "NIKE, Inc.",
      "role": "opponent"
    },
    {
      "name": "Nike Unlimited Care LLC",
      "role": "respondent"
    }
  ]
}