BIZTRAC BETA
Rental and operating of own or leased real estate

SOLÅS AS

Org. no. 927054566 Limited company (AS) Nes Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK −793,000
Equity NOK −839,000
Incorporated 2021
Employees 6
Share capital NOK 100,000

Signals

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

SOLÅS AS is registered as a limited company in Nes, Akershus with organisation number 927054566. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Eie av eiendommer samt prosjektering og bygging av boliger og hytter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK −793,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK −793,000
Equity
NOK −839,000

Financial health · 2025

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

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

Who owns SOLÅS AS?

HÅVARD KVINGE
SOLÅS AS
NOK 2.9m rev. · NOK −793,000 profit

SOLÅS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLÅS AS

Who owns SOLÅS AS?

HÅVARD KVINGE is the largest registered owner, with 100.0%.

What is the revenue of SOLÅS AS?

SOLÅS AS had revenue of NOK 2.9m in 2025.

Who is the general manager of SOLÅS AS?

Håvard Kvinge is registered as general manager of SOLÅS AS.

Where is SOLÅS AS based?

SOLÅS AS has its business address in Årnes.

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.