Who owns the GKODE trademark?

The GKODE trademark is owned by Jackson, Shantez.

What class is the GKODE trademark registered in?

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

What is the serial number for GKODE?

The USPTO serial number for GKODE is 97840351.

What is the registration number for GKODE?

GKODE is registered under USPTO registration number 0.

Sealvo

Home Search: GKODEGKODE #97840351

Back

Updated Sep 29, 2026·23 searches this week

View on USPTO TSDR Find similar marks

GKO

USPTO Trademark Record

PENDING

GKODE

SN 97840351·Reg 0·Filed Mar 15, 2023

Owner Jackson, Shantez

Clothing, footwear, headwear.

GKODE (Serial No. 97840351), Registration No. 0, is a pending US trademark filed on Mar 15, 2023 by Jackson, Shantez. This trademark covers Class 025 (Clothing, footwear & headgear).

Conflict Analysis

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

Mark Intelligence

GKODE (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

Mar 15, 2023

SERIAL

97840351

REG#

REGISTERED

Dec 31, 1969

Filing Information

StatusPENDING

Filing DateMar 15, 2023

Serial Number97840351

Registration No.0

Registration DateDec 31, 1969

Status DateJul 12, 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: Jan 19, 2017

First use in commerce: Jan 19, 2017

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