Opposition · USPTO

Opposition 91187526

OtherUSPTO

Opposition 91187526 at USPTO between PEI Licensing, Inc. and Kookaburra Place, LLC, over the mark THE PLAYFUL PENGUIN, filed Nov 11, 2008. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 11, 2008
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

PEI Licensing, Inc.

Respondent

Kookaburra Place, LLC

Timeline

How the case has moved

Dates from the USPTO record and the THE PLAYFUL PENGUIN filing.

  1. THE PLAYFUL PENGUIN filed

    Application 77406029 filed at the USPTO.
  2. Opposition filed

    PEI Licensing, Inc. started opposition 91187526 at USPTO against THE PLAYFUL PENGUIN.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
THE PLAYFUL PENGUINContested77406029USPTO
[Design mark]Relied on72039655USPTO
[Design mark]Relied on72194637USPTO
[Design mark]Relied on73791911USPTO
PENGUIN CLUBRelied on74236565USPTO
PENGUIN SPORTRelied on74236566USPTO
PENGUIN CLUBRelied on74237323USPTO
[Design mark]Relied on74451688USPTO
PENGUINRelied on76301300USPTO
AN ORIGINAL PENGUIN BY MUNSINGWEARRelied on77139980USPTO
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_b1e8c590-7164-4f3f-8773-e130e346c020
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b1e8c590-7164-4f3f-8773-e130e346c020",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91187526",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-11-11",
  "parties": [
    {
      "name": "PEI Licensing, Inc.",
      "role": "opponent"
    },
    {
      "name": "Kookaburra Place, LLC",
      "role": "respondent"
    }
  ]
}