Opposition · USPTO

Opposition 91300770

OtherUSPTO

Opposition 91300770 at USPTO between Under Armour, Inc. and Lei Zhang, over the mark HERARMOUR, filed Jul 30, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 30, 2025
Marks involved
29
Parties

Who is involved

The parties as named in the office record.

Opponent

Under Armour, Inc.

Company trademarks
Respondent

Lei Zhang

Timeline

How the case has moved

Dates from the USPTO record and the HERARMOUR filing.

  1. HERARMOUR filed

    Application 98716614 filed at the USPTO.
  2. Opposition filed

    Under Armour, Inc. started opposition 91300770 at USPTO against HERARMOUR.
Marks

Marks involved

1 contested mark, 28 marks the challenger relies on.

MarkRoleApplicationOffice
HERARMOURContested98716614USPTO
UNDER ARMOURRelied on75149114USPTO
UNDER ARMOURRelied on76561985USPTO
UNDER ARMOURRelied on77198291USPTO
ARMOUR FLEECERelied on77204256USPTO
UNDER ARMOURRelied on77204292USPTO
ARMOURRelied on77568735USPTO
UNDER ARMOURRelied on77572366USPTO
ARMOUR BRARelied on77585131USPTO
UNDER ARMOURRelied on77589725USPTO
UNDER ARMOURRelied on77590002USPTO
UNDER ARMOURRelied on77690683USPTO

+17 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_d0c1768e-b48b-43cb-a887-d155e0e78334
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d0c1768e-b48b-43cb-a887-d155e0e78334",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300770",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-07-30",
  "parties": [
    {
      "name": "Under Armour,  Inc.",
      "role": "opponent"
    },
    {
      "name": "Lei Zhang",
      "role": "respondent"
    }
  ]
}