Cancellation · USPTO

Cancellation 92092861

PendingUSPTO

Cancellation 92092861 at USPTO between Pure Fishing, Inc. and Fenwick Float-ors, LLC, over the mark FENWICK FLOAT-ORS, filed Sep 18, 2026. Status in the office record: pending.

View FENWICK FLOAT-ORSGet this data via the API
Status
Pending
Filed
Sep 18, 2026
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Petitioner

Pure Fishing, Inc.

Respondent

Fenwick Float-ors, LLC

Timeline

How the case has moved

Dates from the USPTO record and the FENWICK FLOAT-ORS filing.

  1. FENWICK FLOAT-ORS filed

    Application 97803444 filed at the USPTO.

  2. FENWICK FLOAT-ORS registered

  3. Cancellation filed

    Pure Fishing, Inc. started cancellation 92092861 at USPTO against FENWICK FLOAT-ORS.
  4. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
FENWICK FLOAT-ORSContested97803444USPTO
FENWICKRelied on73370939USPTO
FENWICKRelied on73385427USPTO
FENWICKRelied on73387393USPTO
FENWICK EAGLERelied on74067685USPTO
FENWICKRelied on99482171USPTO
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_ddfc39c2-ad7c-4359-86e7-f24cc8666d5f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ddfc39c2-ad7c-4359-86e7-f24cc8666d5f",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92092861",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-09-18",
  "parties": [
    {
      "name": "Pure Fishing, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Fenwick Float-ors, LLC",
      "role": "respondent"
    }
  ]
}