BIZTRAC BETA
Retail sale of cosmetic and toilet articles

HAIRCODE AS

Org. no. 932579839 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 49,000
Operating profit NOK −10,000
Equity NOK −29,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−29k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

HAIRCODE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932579839. The business is classified under retail sale of cosmetic and toilet articles (NACE 47.750). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av handelsvarer via internett og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 49,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 49,000
Operating profit
NOK −10,000
Equity
NOK −29,000

Financial health · 2024

Liquidity
77010.00
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-37.0%
Weak
Equity as a share of total capital

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

Who owns HAIRCODE AS?

ODETA KUKLERYTE
HAIRCODE AS
NOK 49,000 rev. · NOK −10,000 profit

HAIRCODE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAIRCODE AS

Who owns HAIRCODE AS?

ODETA KUKLERYTE is the largest registered owner, with 100.0%.

What is the revenue of HAIRCODE AS?

HAIRCODE AS had revenue of NOK 49,000 in 2024.

Who is the general manager of HAIRCODE AS?

Odeta Kukleryte is registered as general manager of HAIRCODE AS.

Where is HAIRCODE AS based?

HAIRCODE AS has its business address in Trondheim.

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.