Who owns the SMONTY trademark?

The SMONTY trademark is owned by Mame Miya Inc..

What class is the SMONTY trademark registered in?

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

What is the serial number for SMONTY?

The USPTO serial number for SMONTY is 90760165.

What is the registration number for SMONTY?

SMONTY is registered under USPTO registration number 0.

Sealvo

Home Search: SMONTYSMONTY #90760165

Back

Updated Sep 19, 2026·42 searches this week

View on USPTO TSDR Find similar marks

SMO

USPTO Trademark Record

PENDING

SMONTY

SN 90760165·Reg 0·Filed Jun 08, 2021

Owner Mame Miya Inc.

Clothing, footwear, headwear.

SMONTY (Serial No. 90760165), Registration No. 0, is a pending US trademark filed on Jun 08, 2021 by Mame Miya Inc.. This trademark covers Class 025 (Clothing, footwear & headgear).

Conflict Analysis

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

Mark Intelligence

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

FILED

Jun 08, 2021

SERIAL

90760165

REG#

REGISTERED

Dec 31, 1969

Filing Information

StatusPENDING

Filing DateJun 08, 2021

Serial Number90760165

Registration No.0

Registration DateDec 31, 1969

Status DateMay 27, 2026

Mark TypeDesign with words

Filing Basis & Declarations

Filed as Use ApplicationUse Application CurrentlyTrademark

Full Goods & Services

CLASSES

OFFICE

USPTO

COUNTRY

Class 025Clothing, footwear & headgear

US codes: 022, 039

First use anywhere: Nov 06, 2020

First use in commerce: Nov 06, 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

23 events