Opposition · USPTO

Opposition 91195432

OtherUSPTO

Opposition 91195432 at USPTO between Under Armour, Inc. and Luvurday Pty Ltd., over the mark U, filed Jun 23, 2010. Status in the office record: other.

View UGet this data via the API
Status
Other
Result
Other
Filed
Jun 23, 2010
Marks involved
35
Parties

Who is involved

The parties as named in the office record.

Opponent

Under Armour, Inc.

Company trademarks
Respondent

Luvurday Pty Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the U filing.

  1. U filed

    Application 79072287 filed at the USPTO.

  2. Opposition filed

    Under Armour, Inc. started opposition 91195432 at USPTO against U.
Marks

Marks involved

1 contested mark, 34 marks the challenger relies on.

MarkRoleApplicationOffice
UContested79072287USPTO
[Design mark]Relied on75330514USPTO
UA UNDER ARMOURRelied on76157067USPTO
UARelied on76442725USPTO
UA UNDER ARMOURRelied on76561986USPTO
UARelied on76561987USPTO
UARelied on76561988USPTO
UA UNDER ARMOURRelied on76561990USPTO
UARelied on76561992USPTO
UNDER ARMOURRelied on76561993USPTO
UA METALRelied on76566921USPTO
UA METALRelied on76978336USPTO

+23 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_2d1c488f-959e-4845-b400-0df1d5a51ce7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2d1c488f-959e-4845-b400-0df1d5a51ce7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91195432",
  "status": "other",
  "office_code": "US",
  "filed_date": "2010-06-23",
  "parties": [
    {
      "name": "Under Armour, Inc.",
      "role": "opponent"
    },
    {
      "name": "Luvurday Pty Ltd.",
      "role": "respondent"
    }
  ]
}