BIZTRAC BETA
COMPANY REGISTER PROFILE
916096739 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

SOLÅSEN AS

Org. no. 916096739 Limited company (AS) Hyllestad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK −21,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−21k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

SOLÅSEN AS is registered as a limited company in Hyllestad, Vestland with organisation number 916096739. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i og delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▼ −126 %
Equity
NOK −21,000
▲ +41 %

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
47.9%
Very good
Return on total assets
Solidity
-797.7%
Weak
Equity as a share of total capital

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

Who owns SOLÅSEN AS?

SOLÅSEN AS
NOK 0 rev. · NOK −18,000 profit

SOLÅSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLÅSEN AS

Who owns SOLÅSEN AS?

TRYGVE SOLAAS is the largest registered owner, with 100.0%.

What is the revenue of SOLÅSEN AS?

SOLÅSEN AS had revenue of NOK 0 in 2025.

Who is the general manager of SOLÅSEN AS?

Trygve Solaas is registered as general manager of SOLÅSEN AS.

Where is SOLÅSEN AS based?

SOLÅSEN AS has its business address in Leirvik I Sogn.

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.