BIZTRAC BETA
COMPANY REGISTER PROFILE
990933448 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
HAIRCONTRAST AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Hairdressing and barber activities

HAIRCONTRAST AS

Org. no. 990933448 Limited company (AS) Oslo Incorporated 2007 In liquidation
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK −31,000
Equity NOK 373,000
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

HAIRCONTRAST AS is registered as a limited company in Oslo, Oslo with organisation number 990933448. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av frisørsalong og det som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK −31,000
Equity
NOK 373,000

Financial health · 2025

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

Who owns HAIRCONTRAST AS?

HAIRCONTRAST AS
NOK 2.8m rev. · NOK −31,000 profit

HAIRCONTRAST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAIRCONTRAST AS

Who owns HAIRCONTRAST AS?

ZENN AS is the largest registered owner, with 100.0%.

What is the revenue of HAIRCONTRAST AS?

HAIRCONTRAST AS had revenue of NOK 2.8m in 2025.

Where is HAIRCONTRAST AS based?

HAIRCONTRAST 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 02.09.2026.

Report a problem

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