BIZTRAC BETA
Rental and operating of own or leased real estate

SOLA EIENDOM AS

Org. no. 889685522 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 248,000
Operating profit NOK 152,000
Equity NOK 772,000
Incorporated 2006
Share capital NOK 2.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOLA EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 889685522. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 2.1m, divided into 1000 shares. The company's stated purpose is: “Utvikling/bygging av bolig- og næringseiendommer, kjøp og salg av fast eiendom, samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 248,000 in revenue and NOK 152,000 in operating profit.

Key figures · 2024

Revenue
NOK 248,000
Operating profit
NOK 152,000
Equity
NOK 772,000
Est. value
NOK 860,000

Financial health · 2024

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

Who owns SOLA EIENDOM AS?

DINO INVEST AS
SOLA EIENDOM AS
NOK 248,000 rev. · NOK 152,000 profit

SOLA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLA EIENDOM AS

Who owns SOLA EIENDOM AS?

DINO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SOLA EIENDOM AS?

SOLA EIENDOM AS had revenue of NOK 248,000 in 2024.

Where is SOLA EIENDOM AS based?

SOLA EIENDOM AS has its business address in Stavanger.

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.