Opposition · USPTO

Opposition 91224174

OtherUSPTO

Opposition 91224174 at USPTO between DC Comics and Ravensmoon Productions, over the mark 2 8 18 8 36 83.798 KRYPTONITE VAPOR, filed Oct 2, 2015. Status in the office record: other.

View 2 8 18 8 36 83.798 KRYPTONITE VAPORGet this data via the API
Status
Other
Result
Other
Filed
Oct 2, 2015
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

DC Comics

Respondent

Ravensmoon Productions

Timeline

How the case has moved

Dates from the USPTO record and the 2 8 18 8 36 83.798 KRYPTONITE VAPOR filing.

  1. 2 8 18 8 36 83.798 KRYPTONITE VAPOR filed

    Application 86434396 filed at the USPTO.

  2. Opposition filed

    DC Comics started opposition 91224174 at USPTO against 2 8 18 8 36 83.798 KRYPTONITE VAPOR.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
2 8 18 8 36 83.798 KRYPTONITE VAPORContested86434396USPTO
KRYPTORelied on73213453USPTO
SUPERMANRelied on73231827USPTO
KRYPTONITERelied on73242400USPTO
KRYPTONITERelied on75489954USPTO
KRYPTO THE SUPERDOGRelied on78396425USPTO
KRYPTO THE SUPERDOGRelied on78396438USPTO
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_b6940783-7f89-4a08-be1f-d2f656c630be
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b6940783-7f89-4a08-be1f-d2f656c630be",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91224174",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-10-02",
  "parties": [
    {
      "name": "DC Comics",
      "role": "opponent"
    },
    {
      "name": "Ravensmoon Productions",
      "role": "respondent"
    }
  ]
}