Opposition · USPTO

Opposition 91193984

OtherUSPTO

Opposition 91193984 at USPTO between EcoWater Systems LLC and ClearWater Tech, LLC, over the mark ECO3TEX, filed Mar 1, 2010. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 1, 2010
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

EcoWater Systems LLC

Company trademarks
Respondent

ClearWater Tech, LLC

Timeline

How the case has moved

Dates from the USPTO record and the ECO3TEX filing.

  1. ECO3TEX filed

    Application 77694143 filed at the USPTO.
  2. Opposition filed

    EcoWater Systems LLC started opposition 91193984 at USPTO against ECO3TEX.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ECO3TEXContested77694143USPTO
ECODYNERelied on72344041USPTO
ECOCOTERelied on73102786USPTO
ECODEXRelied on73102787USPTO
ECOWATERRelied on73730337USPTO
ECOWATER SYSTEMSRelied on73753845USPTO
ECO PURERelied on73816369USPTO
ECOSORBRelied on74058960USPTO
ECOWATER SYSTEMSRelied on74250958USPTO
ECOWATER SYSTEMSRelied on74277311USPTO
ECOWATERRelied on75154693USPTO
ECOWATER DRINKING WATERRelied on75492829USPTO
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_a03a57eb-092d-49a7-b682-2af4d3e74157
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a03a57eb-092d-49a7-b682-2af4d3e74157",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91193984",
  "status": "other",
  "office_code": "US",
  "filed_date": "2010-03-01",
  "parties": [
    {
      "name": "EcoWater Systems LLC",
      "role": "opponent"
    },
    {
      "name": "ClearWater Tech, LLC",
      "role": "respondent"
    }
  ]
}