Opposition · USPTO

Opposition 91308889

PendingUSPTO

Opposition 91308889 at USPTO between Caterpillar Inc. and Digital Marauders LLC, over the mark CHATCAT, filed Jul 16, 2026. Status in the office record: pending.

Status
Pending
Filed
Jul 16, 2026
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Caterpillar Inc.

Company trademarks
Respondent

Digital Marauders LLC

Timeline

How the case has moved

Dates from the USPTO record and the CHATCAT filing.

  1. CHATCAT filed

    Application 99485686 filed at the USPTO.
  2. Opposition filed

    Caterpillar Inc. started opposition 91308889 at USPTO against CHATCAT.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
CHATCATContested99485686USPTO
CATRelied on71575190USPTO
CATRelied on72137716USPTO
CATRelied on72164427USPTO
CATRelied on72174081USPTO
CATRelied on75550438USPTO
CATRelied on75552003USPTO
CATRelied on75621863USPTO
CATRelied on86976331USPTO
CATRelied on86976333USPTO
CATRelied on86976342USPTO
CATRelied on86976343USPTO

+1 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 /v1/proceedings/{id}
ID=prc_3567d239-eee5-4eeb-95d9-e9065327b1fc
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3567d239-eee5-4eeb-95d9-e9065327b1fc",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91308889",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-07-16",
  "parties": [
    {
      "name": "Caterpillar Inc.",
      "role": "opponent"
    },
    {
      "name": "Digital Marauders LLC",
      "role": "respondent"
    }
  ]
}