Opposition · USPTO

Opposition 91230501

OtherUSPTO

Opposition 91230501 at USPTO between Under Armour, Inc. and Make Ideas LLC, over the mark ARMOR, filed Oct 8, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 8, 2016
Marks involved
26
Parties

Who is involved

The parties as named in the office record.

Opponent

Under Armour, Inc.

Company trademarks
Respondent

Make Ideas LLC

Timeline

How the case has moved

Dates from the USPTO record and the ARMOR filing.

  1. ARMOR filed

    Application 86810774 filed at the USPTO.
  2. Opposition filed

    Under Armour, Inc. started opposition 91230501 at USPTO against ARMOR.
Marks

Marks involved

1 contested mark, 25 marks the challenger relies on.

MarkRoleApplicationOffice
ARMORContested86810774USPTO
UNDER ARMOURRelied on75149114USPTO
UA UNDER ARMOURRelied on76157067USPTO
UNDER ARMOURRelied on76561985USPTO
UNDER ARMOURRelied on76561989USPTO
UNDER ARMOURRelied on76561993USPTO
UNDER ARMOURRelied on77198291USPTO
ARMOUR FLEECERelied on77204256USPTO
UNDER ARMOURRelied on77204292USPTO
ARMOUR STRETCHRelied on77372820USPTO
ARMOURBOUNDRelied on77393742USPTO
ARMOURRelied on77568735USPTO

+14 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_689497f7-ffb2-4b6b-9850-89f920256de3
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_689497f7-ffb2-4b6b-9850-89f920256de3",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91230501",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-10-08",
  "parties": [
    {
      "name": "Under Armour, Inc.",
      "role": "opponent"
    },
    {
      "name": "Make Ideas LLC",
      "role": "respondent"
    }
  ]
}