BIZTRAC BETA
Rental and operating of own or leased real estate

SAO EIENDOM AS

Org. no. 994680307 Limited company (AS) Tromsø Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 2.2m
Equity NOK 223,000
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-11 Adresseendring registrert 2026-03-11.

SAO EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 994680307. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i og forvalte fast eiendom samt utøve aktivt eierskap overfor andre selskaper med liknende formål, samt hertil naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 2.2m
Equity
NOK 223,000
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns SAO EIENDOM AS?

POLARIS EIENDOM NARVIK AS
SAO EIENDOM AS
NOK 6.9m rev. · NOK 2.2m profit

SAO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAO EIENDOM AS

Who owns SAO EIENDOM AS?

POLARIS EIENDOM NARVIK AS is the largest registered owner, with 100.0%.

What is the revenue of SAO EIENDOM AS?

SAO EIENDOM AS had revenue of NOK 6.9m in 2024.

Where is SAO EIENDOM AS based?

SAO 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.