Pharmpur GmbH trademarks
Pharmpur GmbH owns 2 unique trademarks in 1 jurisdiction, combined from 4 owner names in the registers. 2 of them are active.
- Unique trademarks
- 2
- Active100% of unique marks
- 2
- Jurisdictions
- 1
- Owner names grouped
- 4
Where Pharmpur GmbH protects its brands
Each mark counts once here: an international registration is grouped with its country designations, not counted once per country.
By office
- WIPO2100%
By classA mark can cover several classes
Filings per year
New trademarks Pharmpur GmbH has filed each year, counting each mark once.
- Peak year · 1 filed
- 2016
- 2019 to 2023 · filed
- 1
- First filing
- 2016
Filings by year: 2016: 1, 2023: 1.
Latest filings
The most recent applications across Pharmpur GmbH's owner names.
Browse all 2 register records| Mark | Status | Office | Classes | Filed |
|---|---|---|---|---|
| PHARMPUR | registered | WIPO | 1, 5, 10, 37, 39, 40 | 2023-11-06 |
| ophtha futur | mixed | WIPO | 5, 10, 42 | 2016-09-01 |
About Pharmpur GmbH's trademarks
How many trademarks does Pharmpur GmbH own?
Pharmpur GmbH owns 2 unique trademarks across the registers Signa tracks.
How many of Pharmpur GmbH's trademarks are registered?
1 of Pharmpur GmbH's unique marks are registered.
Where does Pharmpur GmbH file the most trademarks?
Pharmpur GmbH holds the most marks at the WIPO, with 2 unique marks.
Get this data via the API
Every number on this page comes from the Signa API. Pull Pharmpur GmbH'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_019eb717-6fec-747d-b9e3-d6324e59c1fb
curl https://api.signa.so/v1/entities/$ID/analytics \
-H "Authorization: Bearer $SIGNA_API_KEY"{
"object": "analytics_report",
"subject": {
"id": "ent_019eb717-6fec-747d-b9e3-d6324e59c1fb",
"object": "entity",
"name": "Pharmpur GmbH"
},
"portfolio": {
"mark_count": 2,
"active_count": 2,
"jurisdiction_spread": {
"WO": 2
}
}
}