Opposition · USPTO

Opposition 91303325

PendingUSPTO

Opposition 91303325 at USPTO between Coulter Ventures, LLC and Intuitive Innovations, LLC, over the mark SYDNEY ROGUE, filed Nov 25, 2025. Status in the office record: pending.

View SYDNEY ROGUEGet this data via the API
Status
Pending
Filed
Nov 25, 2025
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Coulter Ventures, LLC

Company trademarks
Respondent

Intuitive Innovations, LLC

Timeline

How the case has moved

Dates from the USPTO record and the SYDNEY ROGUE filing.

  1. SYDNEY ROGUE filed

    Application 98933250 filed at the USPTO.

  2. Opposition filed

    Coulter Ventures, LLC started opposition 91303325 at USPTO against SYDNEY ROGUE.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
SYDNEY ROGUEContested98933250USPTO
ROGUERelied on78699138USPTO
R YOU ROGUERelied on85681819USPTO
ROGUE SUPPLYRelied on86047006USPTO
ROGUERelied on87375336USPTO
ROGUE SUPPLY CO.Relied on87977396USPTO
ROGUERelied on90220600USPTO
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_6dcf0a32-d80e-4df4-8a36-d498db4aab37
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6dcf0a32-d80e-4df4-8a36-d498db4aab37",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91303325",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-11-25",
  "parties": [
    {
      "name": "Coulter Ventures, LLC",
      "role": "opponent"
    },
    {
      "name": "Intuitive Innovations, LLC",
      "role": "respondent"
    }
  ]
}