Opposition · USPTO

Opposition 91311422

PendingUSPTO

Opposition 91311422 at USPTO between TikTok Ltd. and Shenzhen Shangzhu Technology Co., Ltd., over the mark TITOK, filed Oct 27, 2026. Status in the office record: pending.

Status
Pending
Filed
Oct 27, 2026
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

TikTok Ltd.

Company trademarks
Respondent

Shenzhen Shangzhu Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the TITOK filing.

  1. TITOK filed

    Application 90617104 filed at the USPTO.
  2. Opposition filed

    TikTok Ltd. started opposition 91311422 at USPTO against TITOK.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
TITOKContested90617104USPTO
TIK TOKRelied on87888634USPTO
TIKTOKRelied on88101026USPTO
TIKTOKRelied on88260950USPTO
TIKTOKRelied on88383999USPTO
TIKTOKRelied on88384010USPTO
TIKTOKRelied on88726088USPTO
AS SEEN ON TIKTOK · AS SEEN ON TIKTOK ·Relied on97085320USPTO
AS SEEN ON TIKTOK · AS SEEN ON TIKTOK ·Relied on97085340USPTO
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_2ea36c11-5226-44dc-9fa6-d55359b7f07e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2ea36c11-5226-44dc-9fa6-d55359b7f07e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91311422",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-10-27",
  "parties": [
    {
      "name": "TikTok Ltd.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Shangzhu Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}