biztrac. BETA
COMPANY REGISTER PROFILE
811885282 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SÅ EIGEDOM AS

Org. no. 811885282 Limited company (AS) Stryn Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.2m
Equity NOK 1.8m
Incorporated 2013
Share capital NOK 360,000

SÅ EIGEDOM AS is registered as a limited company in Stryn, Vestland with organisation number 811885282. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 360,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eigedom og forvaltning av eigedom. Samt anna verksemd som fell naturleg inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +31 %
Operating profit
NOK 1.2m
▲ +67 %
Equity
NOK 1.8m
▲ +47 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
6.95
Very good
Current assets ÷ current liabilities
Profitability
14.7%
Good
Return on total assets
Solidity
22.6%
Good
Equity as a share of total capital

Who owns SÅ EIGEDOM AS?

SÅ EIGEDOM AS
NOK 1.6m rev. · NOK 1.2m profit

SÅ EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SÅ EIGEDOM AS own?

SÅ EIGEDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SÅ EIGEDOM AS

Who owns SÅ EIGEDOM AS?

Joar Strand is the largest registered owner, with 50.0%.

What is the revenue of SÅ EIGEDOM AS?

SÅ EIGEDOM AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SÅ EIGEDOM AS?

Ottar Åbrekk is registered as general manager of SÅ EIGEDOM AS.

Where is SÅ EIGEDOM AS based?

SÅ EIGEDOM AS has its business address in Olden.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.