Who owns the FRANK SCOZZESE 601 trademark?

The FRANK SCOZZESE 601 trademark is owned by BALL, S.P.A..

What class is the FRANK SCOZZESE 601 trademark registered in?

The FRANK SCOZZESE 601 trademark is registered in Class 025 (Clothing, footwear & headgear).

What is the serial number for FRANK SCOZZESE 601?

The USPTO serial number for FRANK SCOZZESE 601 is 73618037.

What is the registration number for FRANK SCOZZESE 601?

FRANK SCOZZESE 601 is registered under USPTO registration number 0.

Sealvo

Home Search: FRANK SCOZZESE 601FRANK SCOZZESE 601 #73618037

Back

Updated Oct 10, 2026·10 searches this week

View on USPTO TSDR Find similar marks

FRA

USPTO Trademark Record

ABANDONED

FRANK SCOZZESE 601

SN 73618037·Reg 0·Filed Sep 02, 1986

Owner BALL, S.P.A.

Clothing, footwear, headwear.

FRANK SCOZZESE 601 (Serial No. 73618037), Registration No. 0, is a abandoned US trademark filed on Sep 02, 1986 by BALL, S.P.A.. This trademark covers Class 025 (Clothing, footwear & headgear).

Mark Intelligence

FRANK SCOZZESE 601 (Reg. #0) is an abandoned US trademark that was filed in 1986 but has since been abandoned. The mark covers Class 025 (Clothing, footwear & headgear). Goods and services include Clothing, footwear, headwear.. The mark faced 6 opposition proceedings during prosecution.

FILED

Sep 02, 1986

SERIAL

73618037

REG#

Filing Information

StatusABANDONED

Filing DateSep 02, 1986

Serial Number73618037

Registration No.0

Status DateJun 13, 1989

Published for OppositionSep 15, 1987

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: 039

First use anywhere: Mar 03, 1986

First use in commerce: Mar 07, 1986

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

14 events