Opposition · USPTO

Opposition 91192407

OtherUSPTO

Opposition 91192407 at USPTO between Duramax Marine, LLC and Paragon Airheater Technologies, over the mark DURAMAX, filed Oct 23, 2009. Status in the office record: other.

View DURAMAXGet this data via the API
Status
Other
Result
Other
Filed
Oct 23, 2009
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Duramax Marine, LLC

Company trademarks
Respondent

Paragon Airheater Technologies

Timeline

How the case has moved

Dates from the USPTO record and the DURAMAX filing.

  1. DURAMAX filed

    Application 77745812 filed at the USPTO.

  2. Opposition filed

    Duramax Marine, LLC started opposition 91192407 at USPTO against DURAMAX.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
DURAMAXContested77745812USPTO
DURAMAXRelied on72296024USPTO
DURAMAXRelied on75778192USPTO
DURAMAX MARINERelied on75832588USPTO
DURAMAX INTERNATIONALRelied on75832589USPTO
DURAMAX INDUSTRIALRelied on77180631USPTO
DURAMAXRelied on77180653USPTO
DURAMAX ULTRA-XRelied on77201246USPTO
DURAMAX INTERNATIONALRelied on77846729USPTO
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_fc28e425-a83f-4591-812a-3f843679cdc8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fc28e425-a83f-4591-812a-3f843679cdc8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91192407",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-10-23",
  "parties": [
    {
      "name": "Duramax Marine, LLC",
      "role": "opponent"
    },
    {
      "name": "Paragon Airheater Technologies",
      "role": "respondent"
    }
  ]
}