Cancellation · USPTO

Cancellation 92092218

PendingUSPTO

Cancellation 92092218 at USPTO between Wedbush Securities Inc. and AlphaOne Capital Partners, LLC, over the mark ALPHAONE SATORI FUND, filed Jul 12, 2026. Status in the office record: pending.

View ALPHAONE SATORI FUNDGet this data via the API
Status
Pending
Filed
Jul 12, 2026
Marks involved
3
Parties

Who is involved

The parties as named in the office record.

Petitioner

Wedbush Securities Inc.

Company trademarks
Respondent

AlphaOne Capital Partners, LLC

Timeline

How the case has moved

Dates from the USPTO record and the ALPHAONE SATORI FUND filing.

  1. ALPHAONE SATORI FUND filed

    Application 77806795 filed at the USPTO.

  2. ALPHAONE SATORI FUND registered

  3. Cancellation filed

    Wedbush Securities Inc. started cancellation 92092218 at USPTO against ALPHAONE SATORI FUND.
  4. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 2 marks the challenger relies on.

MarkRoleApplicationOffice
ALPHAONE SATORI FUNDContested77806795USPTO
W ALPHA ONERelied on99348352USPTO
WEDBUSH ALPHA ONERelied on99348355USPTO
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_0a2a9bad-ddaf-422f-8352-a63aff757b81
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0a2a9bad-ddaf-422f-8352-a63aff757b81",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92092218",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-07-12",
  "parties": [
    {
      "name": "Wedbush Securities Inc.",
      "role": "petitioner"
    },
    {
      "name": "AlphaOne Capital Partners, LLC",
      "role": "respondent"
    }
  ]
}