BIZTRAC BETA
Beauty care and other beauty treatment activities

WOWBROW HOLDING AS

Org. no. 933913694 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).
  • Nylig endring 2026-04-22 Adresseendring registrert 2026-04-22.

WOWBROW HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 933913694. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, selskaper, selskapsandeler og fast eiendom samt alt som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 32,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns WOWBROW HOLDING AS?

INDIGO GRUPPEN AS
WOWBROW HOLDING AS
· NOK −6,000 profit

WOWBROW HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does WOWBROW HOLDING AS own?

WOWBROW HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WOWBROW HOLDING AS

Who owns WOWBROW HOLDING AS?

INDIGO GRUPPEN AS is the largest registered owner, with 48.0%.

Who is the general manager of WOWBROW HOLDING AS?

Marco Mladen Bicanic is registered as general manager of WOWBROW HOLDING AS.

Where is WOWBROW HOLDING AS based?

WOWBROW HOLDING AS has its business address in Sandvika.

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.