Opposition · USPTO

Opposition 91205526

OtherUSPTO

Opposition 91205526 at USPTO between Nutri/System IPHC, Inc. and Alticor Inc., over the mark NUTRILITE, filed Jun 11, 2012. Status in the office record: other.

View NUTRILITEGet this data via the API
Status
Other
Result
Other
Filed
Jun 11, 2012
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Nutri/System IPHC, Inc.

Respondent

Alticor Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the NUTRILITE filing.

  1. NUTRILITE filed

    Application 85381035 filed at the USPTO.

  2. Opposition filed

    Nutri/System IPHC, Inc. started opposition 91205526 at USPTO against NUTRILITE.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
NUTRILITEContested85381035USPTO
NUTRISYSTEMRelied on73383698USPTO
NUTRISYSTEMRelied on73606917USPTO
NUTRISYSTEM SILVERRelied on77053256USPTO
NUTRISYSTEM ADVANCEDRelied on77159334USPTO
NUTRISYSTEM BALANCERelied on77538010USPTO
NUTRISYSTEM SELECTRelied on77579847USPTO
NUTRISYSTEM FLEXRelied on77656750USPTO
NUTRISYSTEM MY WAYRelied on77831960USPTO
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_7fee23de-1d7e-4f86-99c6-41dd4d31c99a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7fee23de-1d7e-4f86-99c6-41dd4d31c99a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91205526",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-06-11",
  "parties": [
    {
      "name": "Nutri/System IPHC, Inc.",
      "role": "opponent"
    },
    {
      "name": "Alticor Inc.",
      "role": "respondent"
    }
  ]
}