Opposition · USPTO

Opposition 91294845

OtherUSPTO

Opposition 91294845 at USPTO between Société des Produits Nestlé S.A. and Hong Lu, over the mark NOBLENESTLE, filed Oct 30, 2024. Status in the office record: other.

View NOBLENESTLEGet this data via the API
Status
Other
Result
Other
Filed
Oct 30, 2024
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Société des Produits Nestlé S.A.

Respondent

Hong Lu

Timeline

How the case has moved

Dates from the USPTO record and the NOBLENESTLE filing.

  1. NOBLENESTLE filed

    Application 98385721 filed at the USPTO.

  2. Opposition filed

    Société des Produits Nestlé S.A. started opposition 91294845 at USPTO against NOBLENESTLE.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
NOBLENESTLEContested98385721USPTO
NESTLERelied on71190424USPTO
NESTLERelied on71427167USPTO
NESTLERelied on73163697USPTO
NESTLERelied on73571828USPTO
NESTLERelied on73652919USPTO
NESTLERelied on74017273USPTO
NESTLERelied on75041638USPTO
NESTLERelied on75098953USPTO
NESTLE VITALITYRelied on85967717USPTO
NESTLERelied on86597955USPTO
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_550ac071-0ad2-462e-a205-ebf88b2512f1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_550ac071-0ad2-462e-a205-ebf88b2512f1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294845",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-10-30",
  "parties": [
    {
      "name": "Société des Produits Nestlé S.A.",
      "role": "opponent"
    },
    {
      "name": "Hong Lu",
      "role": "respondent"
    }
  ]
}