Who owns the FIITSROOM trademark?

The FIITSROOM trademark is owned by Jinrui Zhou.

What class is the FIITSROOM trademark registered in?

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

What is the serial number for FIITSROOM?

The USPTO serial number for FIITSROOM is 97725635.

What is the registration number for FIITSROOM?

FIITSROOM is registered under USPTO registration number 7276617.

Sealvo

Home Search: FIITSROOMFIITSROOM #97725635

Back

Updated Oct 10, 2026·8 searches this week

View on USPTO TSDR Find similar marks

FII

USPTO Trademark Record

REGISTERED

FIITSROOM

SN 97725635·Reg 7276617·Filed Dec 20, 2022

Owner Jinrui Zhou

Clothing, footwear, headwear.

FIITSROOM (Serial No. 97725635), Registration No. 7276617, is a registered US trademark filed on Dec 20, 2022 by Jinrui Zhou. This trademark covers Class 025 (Clothing, footwear & headgear).

early section 8: January 16, 2030

Mark Intelligence

FIITSROOM (Reg. #7276617) is a registered US trademark that has been protecting its owner, Jinrui Zhou, since 2022. 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 20, 2022

SERIAL

97725635

REG#

7276617

REGISTERED

Jan 16, 2024

Filing Information

StatusREGISTERED

Filing DateDec 20, 2022

Serial Number97725635

Registration No.7276617

Registration DateJan 16, 2024

Status DateJan 16, 2024

Published for OppositionOct 31, 2023

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 09, 2022

First use in commerce: Nov 09, 2022

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

16 events