Opposition · USPTO

Opposition 91077141

OtherUSPTO

Opposition 91077141 at USPTO between K-Swiss and Liszpar Enterprises, Inc., over the mark KWISKS KUTAIL KWICKLE KRAAZY KLUNKY KRANKY KLAZZY KWIFFY KLAPPY LISZPAR ENTERPRISES INC, filed Nov 16, 1987. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 16, 1987
Marks involved
2
Parties

Who is involved

The parties as named in the office record.

Opponent

K-Swiss

Respondent

Liszpar Enterprises, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the KWISKS KUTAIL KWICKLE KRAAZY KLUNKY KRANKY KLAZZY KWIFFY KLAPPY LISZPAR ENTERPRISES INC filing.

  1. KWISKS KUTAIL KWICKLE KRAAZY KLUNKY KRANKY KLAZZY KWIFFY KLAPPY LISZPAR ENTERPRISES INC filed

    Application 73631385 filed at the USPTO.
  2. Opposition filed

    K-Swiss started opposition 91077141 at USPTO against KWISKS KUTAIL KWICKLE KRAAZY KLUNKY KRANKY KLAZZY KWIFFY KLAPPY LISZPAR ENTERPRISES INC.
Marks

Marks involved

1 contested mark, 1 mark the challenger relies on.

MarkRoleApplicationOffice
KWISKS KUTAIL KWICKLE KRAAZY KLUNKY KRANKY KLAZZY KWIFFY KLAPPY LISZPAR ENTERPRISES INCContested73631385USPTO
K-SWISSRelied on73397232USPTO
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_1b16bb22-3adf-4355-8f6f-915279a22cb6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1b16bb22-3adf-4355-8f6f-915279a22cb6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91077141",
  "status": "other",
  "office_code": "US",
  "filed_date": "1987-11-16",
  "parties": [
    {
      "name": "K-SWISS",
      "role": "opponent"
    },
    {
      "name": "LISZPAR ENTERPRISES,   INC.",
      "role": "respondent"
    }
  ]
}