The Crease Beast, Inc. trademarks
The Crease Beast, Inc. owns 1 unique trademarks in 1 jurisdiction, combined from 6 owner names in the registers. 1 of them are active.
- Unique trademarks
- 1
- Active100% of unique marks
- 1
- Jurisdictions
- 1
- Owner names grouped
- 6
Where The Crease Beast, Inc. protects its brands
Each mark counts once here: an international registration is grouped with its country designations, not counted once per country.
Filings per year
New trademarks The Crease Beast, Inc. has filed each year, counting each mark once.
- Peak year · 1 filed
- 2023
- 2019 to 2023 · filed
- 1
- First filing
- 2023
Filings by year: 2023: 1.
Latest filings
The most recent applications across The Crease Beast, Inc.'s owner names.
Browse all 1 register records| Mark | Status | Office | Classes | Filed |
|---|---|---|---|---|
| CREASE BEAST FLYNESS PROTECTOR | registered | WIPO | 25, 35 | 2023-06-20 |
About The Crease Beast, Inc.'s trademarks
How many trademarks does The Crease Beast, Inc. own?
The Crease Beast, Inc. owns 1 unique trademarks across the registers Signa tracks.
How many of The Crease Beast, Inc.'s trademarks are registered?
1 of The Crease Beast, Inc.'s unique marks are registered.
Where does The Crease Beast, Inc. file the most trademarks?
The Crease Beast, Inc. holds the most marks at the WIPO, with 1 unique marks.
Get this data via the API
Every number on this page comes from the Signa API. Pull The Crease Beast, Inc.'s portfolio into your own product with one request.
GET/v1/entities/{id}/analyticsPortfolio, disputes and ownership changes
GET/v1/entities/{id}Company record, ticker, LEI and owner names
GET/v1/entities/{id}/trademarksEvery trademark in the portfolio
ID=ent_019ebbfc-5222-736e-95a6-4e69a8e01f31
curl https://api.signa.so/v1/entities/$ID/analytics \
-H "Authorization: Bearer $SIGNA_API_KEY"{
"object": "analytics_report",
"subject": {
"id": "ent_019ebbfc-5222-736e-95a6-4e69a8e01f31",
"object": "entity",
"name": "THE CREASE BEAST, INC."
},
"portfolio": {
"mark_count": 1,
"active_count": 1,
"jurisdiction_spread": {
"WO": 1
}
}
}