Opposition · USPTO

Opposition 91183767

OtherUSPTO

Opposition 91183767 at USPTO between Gecko Trading Company, Inc. and Creation Baumann Management AG, over the mark GECKO, filed Apr 24, 2008. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 24, 2008
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Gecko Trading Company, Inc.

Respondent

Creation Baumann Management AG

Timeline

How the case has moved

Dates from the USPTO record and the GECKO filing.

  1. GECKO filed

    Application 79034926 filed at the USPTO.
  2. Opposition filed

    Gecko Trading Company, Inc. started opposition 91183767 at USPTO against GECKO.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
GECKOContested79034926USPTO
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_6a4ae5ed-b5df-4f59-b0c6-342708fc3880
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6a4ae5ed-b5df-4f59-b0c6-342708fc3880",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91183767",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-04-24",
  "parties": [
    {
      "name": "Gecko Trading Company, Inc.",
      "role": "opponent"
    },
    {
      "name": "Creation Baumann Management AG",
      "role": "respondent"
    }
  ]
}