Opposition · USPTO

Opposition 91301731

OtherUSPTO

Opposition 91301731 at USPTO between Pacific World Corporation and Yafang Xie, over the mark TRIMLYX, filed Sep 16, 2025. Status in the office record: other.

View TRIMLYXGet this data via the API
Status
Other
Result
Other
Filed
Sep 16, 2025
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Pacific World Corporation

Company trademarks
Respondent

Yafang Xie

Timeline

How the case has moved

Dates from the USPTO record and the TRIMLYX filing.

  1. TRIMLYX filed

    Application 99073479 filed at the USPTO.

  2. Opposition filed

    Pacific World Corporation started opposition 91301731 at USPTO against TRIMLYX.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
TRIMLYXContested99073479USPTO
TRIMRelied on71647334USPTO
TRIMRelied on71699877USPTO
TRIMRelied on72079212USPTO
TRIMRelied on72131332USPTO
TRIMRelied on72441686USPTO
TRIMRelied on72441695USPTO
TRIMRelied on74008411USPTO
TRIMRelied on74010337USPTO
TRIMRelied on76542829USPTO
TRIMRelied on76568834USPTO
TRIMRelied on90751491USPTO

+3 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_a136ad43-72f6-434a-9729-5bf93835825e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a136ad43-72f6-434a-9729-5bf93835825e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91301731",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-09-16",
  "parties": [
    {
      "name": "Pacific World Corporation",
      "role": "opponent"
    },
    {
      "name": "Yafang Xie",
      "role": "respondent"
    }
  ]
}