Opposition · USPTO

Opposition 91219476

OtherUSPTO

Opposition 91219476 at USPTO between Enterprise Holdings, Inc. and EV World.com, Inc., over the mark EPEDALER, filed Nov 24, 2014. Status in the office record: other.

View EPEDALERGet this data via the API
Status
Other
Result
Other
Filed
Nov 24, 2014
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Enterprise Holdings, Inc.

Company trademarks
Respondent

EV World.com, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the EPEDALER filing.

  1. EPEDALER filed

    Application 86004420 filed at the USPTO.

  2. Opposition filed

    Enterprise Holdings, Inc. started opposition 91219476 at USPTO against EPEDALER.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
EPEDALERContested86004420USPTO
ERelied on72354153USPTO
ERelied on73033536USPTO
ERelied on73346544USPTO
ERelied on74101749USPTO
ERelied on74465251USPTO
ERelied on74465260USPTO
ERelied on75500184USPTO
ERelied on77681395USPTO
ERelied on77789321USPTO
ERelied on77812754USPTO
ERelied on78958766USPTO

+4 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_60339fd9-2029-4e96-b8aa-f9a2989c9be9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_60339fd9-2029-4e96-b8aa-f9a2989c9be9",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91219476",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-11-24",
  "parties": [
    {
      "name": "Enterprise Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "EV World.com, Inc.",
      "role": "respondent"
    }
  ]
}