Who owns the NUPUCY trademark?

The NUPUCY trademark is owned by Xianshu He.

What class is the NUPUCY trademark registered in?

The NUPUCY trademark is registered in Class 025 (Clothing, footwear & headgear).

What is the serial number for NUPUCY?

The USPTO serial number for NUPUCY is 90355933.

What is the registration number for NUPUCY?

NUPUCY is registered under USPTO registration number 6478248.

Sealvo

Home Search: NUPUCYNUPUCY #90355933

Back

Updated Oct 8, 2026·39 searches this week

View on USPTO TSDR Find similar marks

NUP

USPTO Trademark Record

REGISTERED

NUPUCY

SN 90355933·Reg 6478248·Filed Dec 03, 2020

Owner Xianshu He

Clothing, footwear, headwear.

NUPUCY (Serial No. 90355933), Registration No. 6478248, is a registered US trademark filed on Dec 03, 2020 by Xianshu He. This trademark covers Class 025 (Clothing, footwear & headgear).

Renewal window: September 07, 2027333 days remaining

Mark Intelligence

NUPUCY (Reg. #6478248) is a registered US trademark that has been protecting its owner, Xianshu He, since 2020. The mark covers Class 025 (Clothing, footwear & headgear). Goods and services include Clothing, footwear, headwear.. The mark faced 1 opposition proceeding during prosecution.

FILED

Dec 03, 2020

SERIAL

90355933

REG#

6478248

REGISTERED

Sep 07, 2021

Filing Information

StatusREGISTERED

Filing DateDec 03, 2020

Serial Number90355933

Registration No.6478248

Registration DateSep 07, 2021

Status DateSep 07, 2021

Published for OppositionJun 22, 2021

Filing Basis & Declarations

Standard Characters ClaimedFiled as Use ApplicationUse Application CurrentlyTrademark

Full Goods & Services

CLASSES

OFFICE

USPTO

COUNTRY

Class 025Clothing, footwear & headgear

US codes: 022, 039

First use anywhere: Nov 04, 2020

First use in commerce: Nov 04, 2020

Clothing, footwear, headwear.

This description is as filed with the USPTO and defines the scope of trademark protection.

Run a conflict check

Search by serial number, mark name, or logo. See conflicting marks ranked by risk with clear explanations of what contributed.

Run conflict check

Status History

19 events