Cancellation · USPTO

Cancellation 92050579

OtherUSPTO

Cancellation 92050579 at USPTO between EcoWater Systems LLC and GrahamTek Singapore Pte Ltd, over the mark ECONWATER, filed Feb 23, 2009. Status in the office record: other.

View ECONWATERGet this data via the API
Status
Other
Result
Other
Filed
Feb 23, 2009
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Petitioner

EcoWater Systems LLC

Respondent

GrahamTek Singapore Pte Ltd

Timeline

How the case has moved

Dates from the USPTO record and the ECONWATER filing.

  1. ECONWATER filed

    Application 76452063 filed at the USPTO.

  2. ECONWATER registered

  3. Cancellation filed

    EcoWater Systems LLC started cancellation 92050579 at USPTO against ECONWATER.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
ECONWATERContested76452063USPTO
ECOWATERRelied on73730337USPTO
ECOWATER SYSTEMSRelied on73753845USPTO
ECOWATER SYSTEMSRelied on74250958USPTO
ECOWATER SYSTEMSRelied on74277311USPTO
ECOWATERRelied on75154693USPTO
ECOWATER DRINKING WATERRelied on75492829USPTO
ECOWATER SQUADRelied on75668082USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_dc5ceb17-b6a5-4ccd-bb50-bcc7e257d996
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_dc5ceb17-b6a5-4ccd-bb50-bcc7e257d996",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92050579",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-02-23",
  "parties": [
    {
      "name": "EcoWater Systems LLC",
      "role": "petitioner"
    },
    {
      "name": "GrahamTek Singapore Pte Ltd",
      "role": "respondent"
    }
  ]
}