Opposition · USPTO

Opposition 91254892

OtherUSPTO

Opposition 91254892 at USPTO between Under Armour, Inc. and Jiangbei Xu, over the mark UARMOR, filed Mar 26, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 26, 2020
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

Under Armour, Inc.

Company trademarks
Respondent

Jiangbei Xu

Timeline

How the case has moved

Dates from the USPTO record and the UARMOR filing.

  1. UARMOR filed

    Application 88548119 filed at the USPTO.
  2. Opposition filed

    Under Armour, Inc. started opposition 91254892 at USPTO against UARMOR.
Marks

Marks involved

1 contested mark, 23 marks the challenger relies on.

MarkRoleApplicationOffice
UARMORContested88548119USPTO
UNDER ARMOURRelied on75149114USPTO
UA UNDER ARMOURRelied on76157067USPTO
UNDER ARMOURRelied on76561985USPTO
UA UNDER ARMOURRelied on76561990USPTO
UNDER ARMOURRelied on76561993USPTO
UNDER ARMOURRelied on77198291USPTO
UNDER ARMOURRelied on77572366USPTO
UNDER ARMOURRelied on77589725USPTO
UNDER ARMOURRelied on77590002USPTO
UNDER ARMOURRelied on77591154USPTO
ARMOURFUSIONRelied on77626762USPTO

+12 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_7b7ea6a9-5dbb-4570-9f20-d5d00f3c8724
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7b7ea6a9-5dbb-4570-9f20-d5d00f3c8724",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254892",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-03-26",
  "parties": [
    {
      "name": "Under Armour, Inc.",
      "role": "opponent"
    },
    {
      "name": "Jiangbei Xu",
      "role": "respondent"
    }
  ]
}