Who owns the WÜRKIN STIFFS trademark?

The WÜRKIN STIFFS trademark is owned by Wurkin Stiffs Inc..

What class is the WÜRKIN STIFFS trademark registered in?

The WÜRKIN STIFFS trademark is registered in Class 025 (Clothing, footwear & headgear).

What is the serial number for WÜRKIN STIFFS?

The USPTO serial number for WÜRKIN STIFFS is 98397491.

What is the registration number for WÜRKIN STIFFS?

WÜRKIN STIFFS is registered under USPTO registration number 0.

Sealvo

Home Search: WÜRKIN STIFFSWÜRKIN STIFFS #98397491

Back

Updated Sep 27, 2026·21 searches this week

View on USPTO TSDR Find similar marks

WRK

USPTO Trademark Record

PENDING

WÜRKIN STIFFS

SN 98397491·Reg 0·Filed Feb 08, 2024

Owner Wurkin Stiffs Inc.

Clothing, footwear, headwear.

WÜRKIN STIFFS (Serial No. 98397491), Registration No. 0, is a pending US trademark filed on Feb 08, 2024 by Wurkin Stiffs Inc.. This trademark covers Class 025 (Clothing, footwear & headgear).

Conflict Analysis

Full conflict analysis for WÜRKIN STIFFS (SN 98397491) against the USPTO database with detailed risk factor explanations. AI-powered — takes ~1-2 min.

Mark Intelligence

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

FILED

Feb 08, 2024

SERIAL

98397491

REG#

REGISTERED

Dec 31, 1969

Filing Information

StatusPENDING

Filing DateFeb 08, 2024

Serial Number98397491

Registration No.0

Registration DateDec 31, 1969

Status DateJul 12, 2026

Mark TypeStandard characters

Filing Basis & Declarations

Standard Characters ClaimedTrademark

Full Goods & Services

CLASSES

OFFICE

USPTO

COUNTRY

Class 025Clothing, footwear & headgear

US codes: 022, 039

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

18 events