Opposition · USPTO

Opposition 91188363

OtherUSPTO

Opposition 91188363 at USPTO between Gecko Trading Company, Inc. and Gekko Japan Co., Ltd, over the mark 8010 GEKKO, filed Jan 12, 2009. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 12, 2009
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Gecko Trading Company, Inc.

Respondent

Gekko Japan Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the 8010 GEKKO filing.

  1. 8010 GEKKO filed

    Application 77492941 filed at the USPTO.
  2. Opposition filed

    Gecko Trading Company, Inc. started opposition 91188363 at USPTO against 8010 GEKKO.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
8010 GEKKOContested77492941USPTO
GECKORelied on73491536USPTO
GECKORelied on73547750USPTO
MAUI GECKORelied on73662653USPTO
GECKO HAWAIIRelied on74315059USPTO
GECKORelied on74319458USPTO
GECKORelied on74579936USPTO
GECKORelied on75018517USPTO
GECKORelied on75092468USPTO
GECKORelied on75375600USPTO
GECKORelied on75375601USPTO
GECKORelied on75375645USPTO

+4 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_f7259126-7acf-4d8a-b208-76f0fa1b70cc
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f7259126-7acf-4d8a-b208-76f0fa1b70cc",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91188363",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-01-12",
  "parties": [
    {
      "name": "Gecko Trading Company, Inc.",
      "role": "opponent"
    },
    {
      "name": "Gekko Japan Co., Ltd",
      "role": "respondent"
    }
  ]
}