Who owns the SEEMAN BROS. FAMOUS WHITE ROSE PEARS trademark?

The SEEMAN BROS. FAMOUS WHITE ROSE PEARS trademark is owned by WHITE ROSE INC..

What class is the SEEMAN BROS. FAMOUS WHITE ROSE PEARS trademark registered in?

The SEEMAN BROS. FAMOUS WHITE ROSE PEARS trademark is registered in Class 046 (Class 46).

What is the serial number for SEEMAN BROS. FAMOUS WHITE ROSE PEARS?

The USPTO serial number for SEEMAN BROS. FAMOUS WHITE ROSE PEARS is 70023089.

What is the registration number for SEEMAN BROS. FAMOUS WHITE ROSE PEARS?

SEEMAN BROS. FAMOUS WHITE ROSE PEARS is registered under USPTO registration number 23089.

Sealvo

Home Search: SEEMAN BROS. FAMOUS WHITE ROSE PEARSSEEMAN BROS. FAMOUS WHITE ROSE PEARS #70023089

Back

Updated Oct 6, 2026·8 searches this week

View on USPTO TSDR Find similar marks

SEE

USPTO Trademark Record

ABANDONED

SEEMAN BROS. FAMOUS WHITE ROSE PEARS

SN 70023089·Reg 23089·Filed

Owner WHITE ROSE INC.

SEEMAN BROS. FAMOUS WHITE ROSE PEARS (Serial No. 70023089), Registration No. 23089, is a abandoned US trademark by WHITE ROSE INC.. This trademark covers Class 046 (Class 46).

Mark Intelligence

SEEMAN BROS. FAMOUS WHITE ROSE PEARS (Reg. #23089) is an abandoned US trademark that was filed in unknown but has since been abandoned. The mark covers Class 046 (Class 46).

FILED

SERIAL

70023089

REG#

23089

Filing Information

StatusABANDONED

Serial Number70023089

Registration No.23089

Status DateMar 06, 2015

Mark TypeStylized characters

Attorney Docket1333/118

Status DescriptionDead and cancelled, Section 8

Filing Basis & Declarations

Filed as Use ApplicationUse Application CurrentlySection 8 AcceptedTrademark

Full Goods & Services

CLASSES

OFFICE

USPTO

COUNTRY

Class 046Class 46

US codes: 046

First use anywhere: Sep 30, 1887

First use in commerce: Sep 30, 1887

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