Opposition · USPTO

Opposition 91209310

OtherUSPTO

Opposition 91209310 at USPTO between Bayer HealthCare LLC and Bay Game Inc., over the mark THE TRIPPY STIX, filed Feb 13, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 13, 2013
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Bayer HealthCare LLC

Respondent

Bay Game Inc.

Timeline

How the case has moved

Dates from the USPTO record and the THE TRIPPY STIX filing.

  1. THE TRIPPY STIX filed

    Application 85599627 filed at the USPTO.
  2. Opposition filed

    Bayer HealthCare LLC started opposition 91209310 at USPTO against THE TRIPPY STIX.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
THE TRIPPY STIXContested85599627USPTO
CLINISTIXRelied on71690988USPTO
KETOSTIXRelied on72021108USPTO
HEMASTIXRelied on72021109USPTO
GLUCOSTIXRelied on72021111USPTO
ALBUSTIXRelied on72021497USPTO
URISTIXRelied on72039121USPTO
COMBISTIXRelied on72039123USPTO
DIASTIXRelied on72047810USPTO
LABSTIXRelied on72047811USPTO
HEMA-COMBISTIXRelied on72166881USPTO
AZOSTIXRelied on72201640USPTO

+5 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_9de1af9f-4679-4f22-b7e5-c4cb8f85aa8e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9de1af9f-4679-4f22-b7e5-c4cb8f85aa8e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91209310",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-02-13",
  "parties": [
    {
      "name": "Bayer HealthCare LLC",
      "role": "opponent"
    },
    {
      "name": "Bay Game Inc.",
      "role": "respondent"
    }
  ]
}