Opposition · USPTO

Opposition 91228509

OtherUSPTO

Opposition 91228509 at USPTO between Enterprise Holdings, Inc. and E-Force One AG, over the mark E EFORCE, filed Jun 16, 2016. Status in the office record: other.

View E EFORCEGet this data via the API
Status
Other
Result
Other
Filed
Jun 16, 2016
Marks involved
21
Parties

Who is involved

The parties as named in the office record.

Opponent

Enterprise Holdings, Inc.

Company trademarks
Respondent

E-Force One AG

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the E EFORCE filing.

  1. E EFORCE filed

    Application 79162754 filed at the USPTO.

  2. Opposition filed

    Enterprise Holdings, Inc. started opposition 91228509 at USPTO against E EFORCE.
Marks

Marks involved

1 contested mark, 20 marks the challenger relies on.

MarkRoleApplicationOffice
E EFORCEContested79162754USPTO
ERelied on72354153USPTO
ERelied on73033536USPTO
ERelied on74101749USPTO
ERelied on74465251USPTO
ERelied on74465260USPTO
ERelied on75500184USPTO
ERelied on77454676USPTO
ERelied on77681395USPTO
ERelied on77789321USPTO
ERelied on77812754USPTO
ERelied on78958766USPTO

+9 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_83e2ee4e-5b91-4a6f-a9db-0edacfff3a6b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_83e2ee4e-5b91-4a6f-a9db-0edacfff3a6b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91228509",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-06-16",
  "parties": [
    {
      "name": "Enterprise Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "E-Force One AG",
      "role": "respondent"
    }
  ]
}