BIZTRAC BETA
COMPANY REGISTER PROFILE
996094758 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Beauty care and other beauty treatment activities

SALONG HAVBRIS AS

Org. no. 996094758 Limited company (AS) Træna Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 13,000
Operating profit NOK 6,000
Equity NOK −107,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−107k kr).

SALONG HAVBRIS AS is registered as a limited company in Træna, Nordland with organisation number 996094758. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tjenesteyting innenfor velvære og aktiviteter som er relevante i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK 6,000 in operating profit.

Former names: STEIGEN HUD & VELVÆRE AS

Key figures · 2025

Revenue
NOK 13,000
▼ −9 %
Operating profit
NOK 6,000
▲ +29 %
Equity
NOK −107,000
▲ +5 %
Est. value
NOK 26,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
10.4%
Good
Return on total assets
Solidity
-175.7%
Weak
Equity as a share of total capital

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

Who owns SALONG HAVBRIS AS?

SALONG HAVBRIS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALONG HAVBRIS AS

Who owns SALONG HAVBRIS AS?

AINA BRIT KARI WILLUMSEN is the largest registered owner, with 40.0%.

What is the revenue of SALONG HAVBRIS AS?

SALONG HAVBRIS AS had revenue of NOK 13,000 in 2025.

Where is SALONG HAVBRIS AS based?

SALONG HAVBRIS AS has its business address in Træna.

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.