Opposition · USPTO

Opposition 91192000

OtherUSPTO

Opposition 91192000 at USPTO between Kellogg North America Company and Tigerflow Systems, Inc., over the mark [Design Mark], filed Sep 21, 2009. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 21, 2009
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Kellogg North America Company

Respondent

Tigerflow Systems, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 77437966 filed at the USPTO.
  2. Opposition filed

    Kellogg North America Company started opposition 91192000 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested77437966USPTO
TONYRelied on73206492USPTO
TONY'SRelied on74030314USPTO
TONY'S TIGER BITESRelied on74183007USPTO
TONYRelied on75038216USPTO
TONYRelied on75039671USPTO
TONYRelied on75160545USPTO
TONYRelied on78067203USPTO
THE GR-R-REAT TONY BALLOONRelied on78067212USPTO
TONY THE TIGERRelied on78338199USPTO
TIGER POWERRelied on78739246USPTO
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_b7383d10-9f3a-46ec-a2ae-b96bfc3abace
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b7383d10-9f3a-46ec-a2ae-b96bfc3abace",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91192000",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-09-21",
  "parties": [
    {
      "name": "Kellogg North America Company",
      "role": "opponent"
    },
    {
      "name": "Tigerflow Systems, Inc.",
      "role": "respondent"
    }
  ]
}