Cancellation · USPTO

Cancellation 92063484

OtherUSPTO

Cancellation 92063484 at USPTO between ImPACT Applications, Inc. and IW NZ Holdings Limited, over the mark IMPACTWEAR, filed Mar 28, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 28, 2016
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Petitioner

ImPACT Applications, Inc.

Company trademarks
Respondent

IW NZ Holdings Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the IMPACTWEAR filing.

  1. IMPACTWEAR filed

    Application 85440307 filed at the USPTO.
  2. IMPACTWEAR registered

  3. Cancellation filed

    ImPACT Applications, Inc. started cancellation 92063484 at USPTO against IMPACTWEAR.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
IMPACTWEARContested85440307USPTO
IMPACTRelied on85170329USPTO
IMPACTRelied on85170339USPTO
IMPACTRelied on85397900USPTO
IMPACTRelied on85397906USPTO
MOBILE IMPACT CUSTOMER CENTERRelied on85692314USPTO
SIDELINE IMPACTRelied on85977734USPTO
IMCATRelied on85978972USPTO
IMPACT PEDIATRICRelied on86280947USPTO
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_50379f15-b50c-479b-aa0b-851cb490e719
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_50379f15-b50c-479b-aa0b-851cb490e719",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92063484",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-03-28",
  "parties": [
    {
      "name": "ImPACT Applications, Inc.",
      "role": "petitioner"
    },
    {
      "name": "IW NZ Holdings Limited",
      "role": "respondent"
    }
  ]
}