Opposition · USPTO

Opposition 91221981

OtherUSPTO

Opposition 91221981 at USPTO between Nutri/System IPHC, Inc. and NutriMost, over the mark NUTRIMOST, filed May 18, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
May 18, 2015
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Nutri/System IPHC, Inc.

Respondent

NutriMost

Timeline

How the case has moved

Dates from the USPTO record and the NUTRIMOST filing.

  1. NUTRIMOST filed

    Application 86421639 filed at the USPTO.
  2. Opposition filed

    Nutri/System IPHC, Inc. started opposition 91221981 at USPTO against NUTRIMOST.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
NUTRIMOSTContested86421639USPTO
NUTRISYSTEMRelied on73383698USPTO
NUTRISYSTEMRelied on73394040USPTO
NUTRISYSTEMRelied on73606917USPTO
NUTRI/SYSTEMRelied on73685587USPTO
NUTRISYSTEMRelied on74031339USPTO
NUTRISYSTEMRelied on74031485USPTO
NUTRI/SYSTEMRelied on74031752USPTO
NUTRISYSTEMRelied on74218824USPTO
NUTRISYSTEMRelied on77338836USPTO
NUTRISYSTEMRelied on77338865USPTO
NUTRISYSTEMRelied on77338892USPTO

+7 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_17388c5c-8046-410b-b9de-e904c50ec19a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_17388c5c-8046-410b-b9de-e904c50ec19a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91221981",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-05-18",
  "parties": [
    {
      "name": "Nutri/System IPHC, Inc.",
      "role": "opponent"
    },
    {
      "name": "NutriMost",
      "role": "respondent"
    }
  ]
}