Opposition · USPTO

Opposition 91302065

OtherUSPTO

Opposition 91302065 at USPTO between Levi Strauss & Co. and Gaocheng Yu, over the mark LEVIMALL, filed Sep 30, 2025. Status in the office record: other.

View LEVIMALLGet this data via the API
Status
Other
Result
Other
Filed
Sep 30, 2025
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Levi Strauss & Co.

Company trademarks
Respondent

Gaocheng Yu

Timeline

How the case has moved

Dates from the USPTO record and the LEVIMALL filing.

  1. LEVIMALL filed

    Application 99001922 filed at the USPTO.

  2. Opposition filed

    Levi Strauss & Co. started opposition 91302065 at USPTO against LEVIMALL.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
LEVIMALLContested99001922USPTO
LEVI'SRelied on71248368USPTO
LEVI'SRelied on71556108USPTO
LEVI'SRelied on71638273USPTO
LEVI'SRelied on72257497USPTO
LEVI'SRelied on73120559USPTO
LEVI'SRelied on73180144USPTO
LEVI'SRelied on73210408USPTO
LEVI'SRelied on75449347USPTO
LEVI'SRelied on75493759USPTO
LEVI'SRelied on75562738USPTO
LEVI'SRelied on76193799USPTO

+5 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_d577428a-0a10-4d4b-80a9-7f2a8f321c12
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d577428a-0a10-4d4b-80a9-7f2a8f321c12",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302065",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-09-30",
  "parties": [
    {
      "name": "Levi Strauss & Co.",
      "role": "opponent"
    },
    {
      "name": "Gaocheng Yu",
      "role": "respondent"
    }
  ]
}