Opposition · USPTO

Opposition 91205383

OtherUSPTO

Opposition 91205383 at USPTO between EcoWater Systems LLC and Ecotecno S.P.A., over the mark ECOTECNO, filed May 29, 2012. Status in the office record: other.

View ECOTECNOGet this data via the API
Status
Other
Result
Other
Filed
May 29, 2012
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

EcoWater Systems LLC

Company trademarks
Respondent

Ecotecno S.P.A.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the ECOTECNO filing.

  1. ECOTECNO filed

    Application 79093734 filed at the USPTO.

  2. Opposition filed

    EcoWater Systems LLC started opposition 91205383 at USPTO against ECOTECNO.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
ECOTECNOContested79093734USPTO
ECODYNERelied on72344041USPTO
ECOCOTERelied on73102786USPTO
ECODEXRelied on73102787USPTO
ECOWATERRelied on73730337USPTO
ECOWATER SYSTEMSRelied on73753845USPTO
ECO PURERelied on73816369USPTO
ECOWATER SYSTEMSRelied on74250958USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_474712db-479a-42c0-88f0-ef278fd37323
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_474712db-479a-42c0-88f0-ef278fd37323",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91205383",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-05-29",
  "parties": [
    {
      "name": "EcoWater Systems LLC",
      "role": "opponent"
    },
    {
      "name": "Ecotecno S.P.A.",
      "role": "respondent"
    }
  ]
}