BIZTRAC BETA
Wholesale of clothing and footwear

CAMILLA PIHL FASHION GROUP AS

Org. no. 921440588 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 99.3m
Operating profit NOK 1.7m
Equity NOK 13.7m
Incorporated 2018
Employees 54
Share capital NOK 100,000

CAMILLA PIHL FASHION GROUP AS is registered as a limited company in Oslo, Oslo with organisation number 921440588. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2018 and has 54 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Varehandel og produksjon av klær og annet tilbehør, samt annet som naturlig hører inn under dette formål. Kjøp og salg av aksjer, samt deltakelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 99.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 99.3m
Operating profit
NOK 1.7m
Equity
NOK 13.7m
Est. value
NOK 11.4m

Financial health · 2024

Liquidity
1.69
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.5%
Good
Equity as a share of total capital

Who owns CAMILLA PIHL FASHION GROUP AS?

PETERS & PIHL HOLDING AS
CAMILLA PIHL FASHION GROUP AS
NOK 99.3m rev. · NOK 1.7m profit

CAMILLA PIHL FASHION GROUP AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about CAMILLA PIHL FASHION GROUP AS

Who owns CAMILLA PIHL FASHION GROUP AS?

PETERS & PIHL HOLDING AS is the largest registered owner, with 38.0%.

What is the revenue of CAMILLA PIHL FASHION GROUP AS?

CAMILLA PIHL FASHION GROUP AS had revenue of NOK 99.3m in 2024.

Where is CAMILLA PIHL FASHION GROUP AS based?

CAMILLA PIHL FASHION GROUP AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.