Cancellation · USPTO

Cancellation 92081623

OtherUSPTO

Cancellation 92081623 at USPTO between Vans, Inc. and Shenzhen Hongxinchao Trading Co., Ltd, over the mark VANSHA, filed Feb 17, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 17, 2023
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Petitioner

Vans, Inc.

Company trademarks
Respondent

Shenzhen Hongxinchao Trading Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the VANSHA filing.

  1. VANSHA filed

    Application 87589189 filed at the USPTO.
  2. VANSHA registered

  3. Cancellation filed

    Vans, Inc. started cancellation 92081623 at USPTO against VANSHA.
Marks

Marks involved

1 contested mark, 21 marks the challenger relies on.

MarkRoleApplicationOffice
VANSHAContested87589189USPTO
VANSRelied on73396311USPTO
VANSRelied on73396312USPTO
VANSRelied on73396323USPTO
VANSRelied on73399859USPTO
VANSRelied on73441417USPTO
VANSRelied on74239429USPTO
VANSRelied on74458715USPTO
VANSRelied on74458716USPTO
VANSRelied on77802906USPTO
VANSRelied on77802957USPTO
VANSRelied on77803104USPTO

+10 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_5dd54c00-325e-46ab-9b39-3d1adcc40dea
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5dd54c00-325e-46ab-9b39-3d1adcc40dea",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92081623",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-02-17",
  "parties": [
    {
      "name": "Vans, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Shenzhen Hongxinchao Trading Co., Ltd",
      "role": "respondent"
    }
  ]
}