BIZTRAC BETA
Development of building projects

SOLNESSET EIENDOM AS

Org. no. 991453199 Limited company (AS) Tromsø Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −938,000
Equity NOK 13.3m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−938k kr).

SOLNESSET EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 991453199. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom. Eiendomsutvikling. Utleie av eiendom. Investering i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −938,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −938,000
Equity
NOK 13.3m
Est. value
NOK 12.1m

Financial health · 2024

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.0%
Satisfactory
Equity as a share of total capital

Who owns SOLNESSET EIENDOM AS?

LOKE AS
SOLNESSET EIENDOM AS
NOK 1.0m rev. · NOK −938,000 profit

SOLNESSET EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SOLNESSET EIENDOM AS own?

SOLNESSET EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SOLNESSET EIENDOM AS

Who owns SOLNESSET EIENDOM AS?

LOKE AS is the largest registered owner, with 40.0%.

What is the revenue of SOLNESSET EIENDOM AS?

SOLNESSET EIENDOM AS had revenue of NOK 1.0m in 2024.

Where is SOLNESSET EIENDOM AS based?

SOLNESSET EIENDOM AS has its business address in Tromsø.

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.