Opposition · USPTO

Opposition 91299673

OtherUSPTO

Opposition 91299673 at USPTO between LEGO Holding A/S and Shenzhen Huanle Yigou Technology Co., Ltd., over the mark HANLEGO, filed Jun 11, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 11, 2025
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

LEGO Holding A/S

Company trademarks
Respondent

Shenzhen Huanle Yigou Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the HANLEGO filing.

  1. HANLEGO filed

    Application 98607529 filed at the USPTO.
  2. Opposition filed

    LEGO Holding A/S started opposition 91299673 at USPTO against HANLEGO.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
HANLEGOContested98607529USPTO
LEGORelied on73032292USPTO
LEGORelied on73032295USPTO
LEGORelied on73369522USPTO
LEGORelied on73370524USPTO
LEGORelied on73703593USPTO
LEGORelied on73738309USPTO
LEGORelied on74227042USPTO
LEGORelied on74482858USPTO
LEGORelied on74544115USPTO
LEGORelied on74593028USPTO
LEGORelied on75027872USPTO

+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 /v1/proceedings/{id}
ID=prc_70dbe93e-8c68-42c8-b49c-d5717fa17a26
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_70dbe93e-8c68-42c8-b49c-d5717fa17a26",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299673",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-06-11",
  "parties": [
    {
      "name": "LEGO Holding A/S",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Huanle Yigou Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}