Opposition · USPTO

Opposition 91307195

OtherUSPTO

Opposition 91307195 at USPTO between Pop Mart (Singapore) Holding Pte. Ltd. and PopX Labs Limited, over the mark POP X, filed May 8, 2026. Status in the office record: other.

View POP XGet this data via the API
Status
Other
Result
Other
Filed
May 8, 2026
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Pop Mart (Singapore) Holding Pte. Ltd.

Respondent

PopX Labs Limited

Timeline

How the case has moved

Dates from the USPTO record and the POP X filing.

  1. POP X filed

    Application 99298131 filed at the USPTO.

  2. Opposition filed

    Pop Mart (Singapore) Holding Pte. Ltd. started opposition 91307195 at USPTO against POP X.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
POP XContested99298131USPTO
POP CUBERelied on79432022USPTO
POP NOWRelied on79436245USPTO
POPBEANRelied on79437244USPTO
POPOPRelied on79438999USPTO
POP MART ROBO SHOPRelied on79440957USPTO
POP MARTRelied on88903522USPTO
POP MARTRelied on98088986USPTO
POP STARRelied on99220021USPTO
POP LANDRelied on99286760USPTO
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_12553482-e7ce-4791-a9b9-e5039db9025c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_12553482-e7ce-4791-a9b9-e5039db9025c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91307195",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-05-08",
  "parties": [
    {
      "name": "POP MART (SINGAPORE) HOLDING PTE. LTD.",
      "role": "opponent"
    },
    {
      "name": "PopX Labs Limited",
      "role": "respondent"
    }
  ]
}