biztrac. BETA
COMPANY REGISTER PROFILE
920432395 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of cosmetic and toilet articles

IGLOW COSMETICS AS

Org. no. 920432395 Limited company (AS) Bergen Incorporated 2018 Active
Revenue 2025 NOK 17.1m
Operating profit NOK −149,000
Equity NOK 2.5m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−149k kr).

IGLOW COSMETICS AS is registered as a limited company in Bergen, Vestland with organisation number 920432395. The business is classified under retail sale of cosmetic and toilet articles (NACE 47.750). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Salg av varer over internett, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.1m in revenue and NOK −149,000 in operating profit.

Key figures · 2025

Revenue
NOK 17.1m
▼ −28 %
Operating profit
NOK −149,000
▼ −392 %
Equity
NOK 2.5m
▼ −1 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
41.4%
Very good
Equity as a share of total capital

Who owns IGLOW COSMETICS AS?

IGLOW COSMETICS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about IGLOW COSMETICS AS

Who owns IGLOW COSMETICS AS?

BRA AINVEST AS is the largest registered owner, with 30.0%.

What is the revenue of IGLOW COSMETICS AS?

IGLOW COSMETICS AS had revenue of NOK 17.1m in 2025.

Who is the general manager of IGLOW COSMETICS AS?

Elin Reed Bratten is registered as general manager of IGLOW COSMETICS AS.

Where is IGLOW COSMETICS AS based?

IGLOW COSMETICS AS has its business address in Bergen.

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

Report a problem

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