Opposition · USPTO

Opposition 91248788

OtherUSPTO

Opposition 91248788 at USPTO between Under Armour, Inc. and Fu Xiaohua, over the mark ANNMAH, filed Jun 5, 2019. Status in the office record: other.

View ANNMAHGet this data via the API
Status
Other
Result
Other
Filed
Jun 5, 2019
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Under Armour, Inc.

Company trademarks
Respondent

Fu Xiaohua

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the ANNMAH filing.

  1. ANNMAH filed

    Application 79254242 filed at the USPTO.

  2. Opposition filed

    Under Armour, Inc. started opposition 91248788 at USPTO against ANNMAH.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
ANNMAHContested79254242USPTO
UA UNDER ARMOURRelied on76157067USPTO
UARelied on76442725USPTO
UA UNDER ARMOURRelied on76561986USPTO
UARelied on76561987USPTO
UARelied on76561988USPTO
UNDER ARMOURRelied on76561993USPTO
UARelied on77590034USPTO
UARelied on77590378USPTO
UARelied on77917981USPTO
UARelied on77918131USPTO
U ARelied on78674048USPTO

+3 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_e9f1a274-0ff1-4562-a7a2-2a82036e361c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e9f1a274-0ff1-4562-a7a2-2a82036e361c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91248788",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-06-05",
  "parties": [
    {
      "name": "Under Armour, Inc.",
      "role": "opponent"
    },
    {
      "name": "Fu Xiaohua",
      "role": "respondent"
    }
  ]
}