BIZTRAC BETA
Rental and operating of own or leased real estate

SISO EIENDOM AS

Org. no. 921839502 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 385,000
Equity NOK 1.4m
Incorporated 2018
Share capital NOK 300,000

SISO EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 921839502. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drive utleie av eiendom, kjøp og salg av eiendom, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 385,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 385,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
2.24
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

Who owns SISO EIENDOM AS?

SEBERG INVEST AS
SISO EIENDOM AS
NOK 1.2m rev. · NOK 385,000 profit

SISO EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SISO EIENDOM AS own?

SISO EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SISO EIENDOM AS

Who owns SISO EIENDOM AS?

SEBERG INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of SISO EIENDOM AS?

SISO EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of SISO EIENDOM AS?

Ingvar Orten is registered as general manager of SISO EIENDOM AS.

Where is SISO EIENDOM AS based?

SISO EIENDOM AS has its business address in Kristiansand S.

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.