Opposition · USPTO

Opposition 91265837

OtherUSPTO

Opposition 91265837 at USPTO between Lenzing Aktiengesellschaft and Nanjing Tengshi Information Technology Co., Ltd., over the mark TENSELL, filed Nov 6, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 6, 2020
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Lenzing Aktiengesellschaft

Company trademarks
Respondent

Nanjing Tengshi Information Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the TENSELL filing.

  1. TENSELL filed

    Application 88823374 filed at the USPTO.
  2. Opposition filed

    Lenzing Aktiengesellschaft started opposition 91265837 at USPTO against TENSELL.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
TENSELLContested88823374USPTO
TENCELRelied on73662820USPTO
TENCELRelied on75288904USPTO
TENCELRelied on79083651USPTO
TENCEL BIOSOFTRelied on79139218USPTO
TENCELWEBRelied on86081602USPTO
TENCELRelied on87361497USPTO
TENCELRelied on87519593USPTO
TENCELRelied on87780524USPTO
TENCELRelied on88977364USPTO
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_fb5b2066-b518-4f44-84ec-fb517fba88eb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fb5b2066-b518-4f44-84ec-fb517fba88eb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91265837",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-11-06",
  "parties": [
    {
      "name": "Lenzing Aktiengesellschaft",
      "role": "opponent"
    },
    {
      "name": "Nanjing Tengshi Information Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}