Opposition · USPTO

Opposition 91306450

PendingUSPTO

Opposition 91306450 at USPTO between Inseco, Inc. and Shingle RX, LLC, over the mark SHINGLE RX, filed Apr 8, 2026. Status in the office record: pending.

Status
Pending
Filed
Apr 8, 2026
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Inseco, Inc.

Respondent

Shingle RX, LLC

Timeline

How the case has moved

Dates from the USPTO record and the SHINGLE RX filing.

  1. SHINGLE RX filed

    Application 99246641 filed at the USPTO.
  2. Opposition filed

    Inseco, Inc. started opposition 91306450 at USPTO against SHINGLE RX.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
SHINGLE RXContested99246641USPTO
WOOD RXRelied on75037013USPTO
SEALRXRelied on87640210USPTO
WOODRXRelied on87781935USPTO
NPSRXRelied on87781962USPTO
DECKRXRelied on87781976USPTO
PAVER SEAL RXRelied on87781990USPTO
NPS RXRelied on90002147USPTO
SEALRXRelied on90108905USPTO
SEALRXRelied on90108929USPTO
ROOF RXRelied on97026092USPTO
ROOF SEAL RXRelied on97026103USPTO

+4 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_bbad7609-917d-4e7c-82a4-d90fb064507e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bbad7609-917d-4e7c-82a4-d90fb064507e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306450",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-04-08",
  "parties": [
    {
      "name": "Inseco, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shingle RX, LLC",
      "role": "respondent"
    }
  ]
}