Who owns the I'UMI trademark?

The I'UMI trademark is owned by INCOPAFUL INC..

What class is the I'UMI trademark registered in?

The I'UMI trademark is registered in Class 025 (Clothing, footwear & headgear).

What is the serial number for I'UMI?

The USPTO serial number for I'UMI is 98233564.

What is the registration number for I'UMI?

I'UMI is registered under USPTO registration number 0.

Sealvo

Home Search: I'UMII'UMI #98233564

Back

Updated Sep 20, 2026·17 searches this week

View on USPTO TSDR Find similar marks

IUM

USPTO Trademark Record

PENDING

I'UMI

SN 98233564·Reg 0·Filed Oct 20, 2023

Owner INCOPAFUL INC.

Clothing, footwear, headwear.

I'UMI (Serial No. 98233564), Registration No. 0, is a pending US trademark filed on Oct 20, 2023 by INCOPAFUL INC.. This trademark covers Class 025 (Clothing, footwear & headgear).

Conflict Analysis

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

Mark Intelligence

I'UMI (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

Oct 20, 2023

SERIAL

98233564

REG#

REGISTERED

Dec 31, 1969

Filing Information

StatusPENDING

Filing DateOct 20, 2023

Serial Number98233564

Registration No.0

Registration DateDec 31, 1969

Status DateJul 27, 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: Oct 01, 2023

First use in commerce: Oct 01, 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

17 events