BIZTRAC BETA
Development of building projects

SØSTRENE HINNA UTBYGGING AS

Org. no. 924463511 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 18.6m
Operating profit NOK 247,000
Equity NOK 397,000
Incorporated 2019
Share capital NOK 30,000

SØSTRENE HINNA UTBYGGING AS is registered as a limited company in Stavanger, Rogaland with organisation number 924463511. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å eie og utvikle fast eiendom, samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.6m in revenue and NOK 247,000 in operating profit.

Key figures · 2025

Revenue
NOK 18.6m
Operating profit
NOK 247,000
Equity
NOK 397,000
Est. value
NOK 804,000

Financial health · 2024

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

Who owns SØSTRENE HINNA UTBYGGING AS?

ØGREID EIENDOM AS
SØSTRENE HINNA UTBYGGING AS
NOK 18.6m rev. · NOK 247,000 profit

SØSTRENE HINNA UTBYGGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØSTRENE HINNA UTBYGGING AS

Who owns SØSTRENE HINNA UTBYGGING AS?

ØGREID EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SØSTRENE HINNA UTBYGGING AS?

SØSTRENE HINNA UTBYGGING AS had revenue of NOK 18.6m in 2025.

Who is the general manager of SØSTRENE HINNA UTBYGGING AS?

Erlend Løge Aanestad is registered as general manager of SØSTRENE HINNA UTBYGGING AS.

Where is SØSTRENE HINNA UTBYGGING AS based?

SØSTRENE HINNA UTBYGGING 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.