Cancellation · USPTO

Cancellation 92088963

OtherUSPTO

Cancellation 92088963 at USPTO between Fox Factory, Inc. and Huang Yiqun, over the mark ARCFOX, filed Jul 16, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 16, 2025
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Petitioner

Fox Factory, Inc.

Company trademarks
Respondent

Huang Yiqun

Timeline

How the case has moved

Dates from the USPTO record and the ARCFOX filing.

  1. ARCFOX filed

    Application 97073284 filed at the USPTO.
  2. ARCFOX registered

  3. Cancellation filed

    Fox Factory, Inc. started cancellation 92088963 at USPTO against ARCFOX.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
ARCFOXContested97073284USPTO
FOXRelied on75607852USPTO
FOXRelied on75613056USPTO
FOXRelied on77664984USPTO
FOX RACING SHOXRelied on78239008USPTO
FOXRelied on85232917USPTO
FOX RACING SHOXRelied on85361080USPTO
FOX PERFORMANCE SERIESRelied on85525986USPTO
FOX DEFENSERelied on85983399USPTO
FOX FACTORYRelied on87630620USPTO
FOX FACTORYRelied on87630628USPTO
FOXRelied on87977518USPTO

+2 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_ab31fe81-89a0-448b-a024-4d57608f6073
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ab31fe81-89a0-448b-a024-4d57608f6073",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92088963",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-07-16",
  "parties": [
    {
      "name": "Fox Factory, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Huang Yiqun",
      "role": "respondent"
    }
  ]
}