Who owns the HLWOYYE trademark?

The HLWOYYE trademark is owned by Ling Lu.

What class is the HLWOYYE trademark registered in?

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

What is the serial number for HLWOYYE?

The USPTO serial number for HLWOYYE is 98008157.

What is the registration number for HLWOYYE?

HLWOYYE is registered under USPTO registration number 0.

Sealvo

Home Search: HLWOYYEHLWOYYE #98008157

Back

Updated Sep 22, 2026·22 searches this week

View on USPTO TSDR Find similar marks

HLW

USPTO Trademark Record

PENDING

HLWOYYE

SN 98008157·Reg 0·Filed May 22, 2023

Owner Ling Lu

Clothing, footwear, headwear.

HLWOYYE (Serial No. 98008157), Registration No. 0, is a pending US trademark filed on May 22, 2023 by Ling Lu. This trademark covers Class 025 (Clothing, footwear & headgear).

Conflict Analysis

Full conflict analysis for HLWOYYE (SN 98008157) against the USPTO database with detailed risk factor explanations. AI-powered — takes ~1-2 min.

Mark Intelligence

HLWOYYE (Reg. #0) is a pending US trademark that was filed in 2023 and is currently under USPTO examination. The mark covers Class 025 (Clothing, footwear & headgear). Goods and services include Clothing, footwear, headwear..

FILED

May 22, 2023

SERIAL

98008157

REG#

REGISTERED

Dec 31, 1969

Filing Information

StatusPENDING

Filing DateMay 22, 2023

Serial Number98008157

Registration No.0

Registration DateDec 31, 1969

Status DateJun 01, 2026

Mark TypeStandard characters

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: May 02, 2023

First use in commerce: May 02, 2023

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

20 events