Opposition · USPTO

Opposition 91310048

PendingUSPTO

Opposition 91310048 at USPTO between Mattel, Inc. and Nazia Mashriqi, over the mark HIJARBIE, filed Sep 1, 2026. Status in the office record: pending.

Status
Pending
Filed
Sep 1, 2026
Marks involved
42
Parties

Who is involved

The parties as named in the office record.

Opponent

Mattel, Inc.

Company trademarks
Respondent

Nazia Mashriqi

Timeline

How the case has moved

Dates from the USPTO record and the HIJARBIE filing.

  1. HIJARBIE filed

    Application 99750419 filed at the USPTO.
  2. Opposition filed

    Mattel, Inc. started opposition 91310048 at USPTO against HIJARBIE.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 41 marks the challenger relies on.

MarkRoleApplicationOffice
HIJARBIEContested99750419USPTO
BARBIERelied on72055200USPTO
BARBIERelied on72106619USPTO
BARBIERelied on72152228USPTO
BARBIERelied on72166825USPTO
BARBIERelied on72179913USPTO
BARBIERelied on72210579USPTO
BARBIERelied on72211370USPTO
BARBIERelied on72211372USPTO
BARBIERelied on73019358USPTO
BARBIERelied on73052196USPTO
BARBIERelied on73455560USPTO

+30 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_ff142ddd-0e55-4b55-9cbb-ec9e713212ad
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ff142ddd-0e55-4b55-9cbb-ec9e713212ad",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91310048",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-09-01",
  "parties": [
    {
      "name": "MATTEL, INC.",
      "role": "opponent"
    },
    {
      "name": "Nazia Mashriqi",
      "role": "respondent"
    }
  ]
}