Opposition · USPTO

Opposition 91295058

OtherUSPTO

Opposition 91295058 at USPTO between DC Comics and Truox, Inc., over the mark KRYPTONITE FOR RWI, filed Nov 11, 2024. Status in the office record: other.

View KRYPTONITE FOR RWIGet this data via the API
Status
Other
Result
Other
Filed
Nov 11, 2024
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

DC Comics

Respondent

Truox, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the KRYPTONITE FOR RWI filing.

  1. KRYPTONITE FOR RWI filed

    Application 98228698 filed at the USPTO.

  2. Opposition filed

    DC Comics started opposition 91295058 at USPTO against KRYPTONITE FOR RWI.
Marks

Marks involved

3 contested marks, 7 marks the challenger relies on.

MarkRoleApplicationOffice
KRYPTONITE FOR RWIContested98228698USPTO
KRYPTONITE FOR RECREATIONAL WATER ILLNESSContested98228723USPTO
KRYPTONITE TO RWIContested98285167USPTO
KRYPTORelied on73213453USPTO
KRYPTONITERelied on73242400USPTO
KRYPTONITERelied on75489954USPTO
KRYPTO THE SUPERDOGRelied on78396425USPTO
KRYPTO THE SUPERDOGRelied on78396438USPTO
KRYPTONRelied on86955637USPTO
KRYPTONRelied on86955645USPTO
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_4b10162b-15a0-4ef0-a53f-087dc310ad10
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4b10162b-15a0-4ef0-a53f-087dc310ad10",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91295058",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-11-11",
  "parties": [
    {
      "name": "DC Comics",
      "role": "opponent"
    },
    {
      "name": "Truox, Inc.",
      "role": "respondent"
    }
  ]
}