BIZTRAC BETA
Operation of sports facilities

SOLHEISEN AS

Org. no. 871225982 Limited company (AS) Hemsedal Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK −5.5m
Equity NOK −15.3m
Incorporated 1994
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−15,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,5 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOLHEISEN AS is registered as a limited company in Hemsedal, Buskerud with organisation number 871225982. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drift av skiheiser, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK −5.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK −5.5m
Equity
NOK −15.3m

Financial health · 2024

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

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

Who owns SOLHEISEN AS?

SOLHEISEN UTVIKLING AS
SOLHEISEN AS
NOK 7.6m rev. · NOK −5.5m profit

SOLHEISEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLHEISEN AS

Who owns SOLHEISEN AS?

SOLHEISEN UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of SOLHEISEN AS?

SOLHEISEN AS had revenue of NOK 7.6m in 2024.

Where is SOLHEISEN AS based?

SOLHEISEN AS has its business address in Hemsedal.

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.