Opposition · USPTO

Opposition 91197712

OtherUSPTO

Opposition 91197712 at USPTO between Kellogg North America Company and Perk-Up, Inc., over the mark SUPER K, filed Dec 6, 2010. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 6, 2010
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Opponent

Kellogg North America Company

Respondent

Perk-Up, Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SUPER K filing.

  1. SUPER K filed

    Application 77914991 filed at the USPTO.
  2. Opposition filed

    Kellogg North America Company started opposition 91197712 at USPTO against SUPER K.
Marks

Marks involved

2 contested marks, 20 marks the challenger relies on.

MarkRoleApplicationOffice
SUPER KContested77914991USPTO
SUPER K BRANDContested77915024USPTO
KELLOGGSRelied on71400819USPTO
KELLOGG'SRelied on71452907USPTO
KELLOGG'SRelied on71452908USPTO
SPECIAL KRelied on71686658USPTO
KRelied on73395148USPTO
KRelied on73395402USPTO
SPECIAL KRelied on74129398USPTO
SPECIAL KRelied on74381328USPTO
KRelied on75343041USPTO
FUN K TOWNRelied on77021286USPTO

+10 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_7e8f734e-9c5b-46f0-b87c-b76cc9678b75
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7e8f734e-9c5b-46f0-b87c-b76cc9678b75",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91197712",
  "status": "other",
  "office_code": "US",
  "filed_date": "2010-12-06",
  "parties": [
    {
      "name": "Kellogg North America Company",
      "role": "opponent"
    },
    {
      "name": "Perk-Up, Inc.",
      "role": "respondent"
    }
  ]
}