BIZTRAC BETA
Rental and operating of own or leased real estate

SATE EIENDOM AS

Org. no. 990016348 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 6.1m
Equity NOK 13.6m
Incorporated 2006
Share capital NOK 1.9m

SATE EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 990016348. 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 1.9m, divided into 100 shares. The company's stated purpose is: “Drive investering i, samt omsetning og utleie av fast eiendom, samt å investere i selskaper som driver lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 6.1m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 6.1m
Equity
NOK 13.6m
Est. value
NOK 19.7m

Financial health · 2024

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.9%
Good
Equity as a share of total capital

Who owns SATE EIENDOM AS?

SVEIN ARILD SKÅLAND
SATE EIENDOM AS
NOK 8.2m rev. · NOK 6.1m profit

SATE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SATE EIENDOM AS own?

SATE EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SATE EIENDOM AS

Who owns SATE EIENDOM AS?

SVEIN ARILD SKÅLAND is the largest registered owner, with 50.0%.

What is the revenue of SATE EIENDOM AS?

SATE EIENDOM AS had revenue of NOK 8.2m in 2024.

Who is the general manager of SATE EIENDOM AS?

Terje Skåland is registered as general manager of SATE EIENDOM AS.

Where is SATE EIENDOM AS based?

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