Opposition · USPTO

Opposition 91183716

OtherUSPTO

Opposition 91183716 at USPTO between Enterprise Rent-A-Car Company and Randall-Reilly Publishing Company, LLC, over the mark ETRUCKER, filed Apr 23, 2008. Status in the office record: other.

View ETRUCKERGet this data via the API
Status
Other
Result
Other
Filed
Apr 23, 2008
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Enterprise Rent-A-Car Company

Respondent

Randall-Reilly Publishing Company, LLC

Timeline

How the case has moved

Dates from the USPTO record and the ETRUCKER filing.

  1. ETRUCKER filed

    Application 77238423 filed at the USPTO.

  2. Opposition filed

    Enterprise Rent-A-Car Company started opposition 91183716 at USPTO against ETRUCKER.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
ETRUCKERContested77238423USPTO
ERelied on72354153USPTO
ERelied on73033536USPTO
ERelied on73346544USPTO
ERelied on74101749USPTO
E ENTERPRISERelied on74255784USPTO
ERelied on74465251USPTO
ERelied on74465260USPTO
E ENTERPRISERelied on75031616USPTO
ERelied on75500184USPTO
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_7338f506-4974-4603-b95c-30f9af736e69
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7338f506-4974-4603-b95c-30f9af736e69",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91183716",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-04-23",
  "parties": [
    {
      "name": "Enterprise Rent-A-Car Company",
      "role": "opponent"
    },
    {
      "name": "Randall-Reilly Publishing Company, LLC",
      "role": "respondent"
    }
  ]
}