BIZTRAC BETA
Development of building projects

SKÅRER BOLIG AS

Org. no. 990212929 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 774.1m
Operating profit NOK 105.8m
Equity NOK 76.8m
Incorporated 2006
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SKÅRER BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 990212929. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Eie, leie, utleie, utvikle, forvalte, drifte og investere i fast eiendom eller selskaper som eier fast eiendom, samt andre aktiviteter forbundet med dette, herunder oppta lån fra selskaper i samme konsern for å finansiere virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 774.1m in revenue and NOK 105.8m in operating profit.

Key figures · 2024

Revenue
NOK 774.1m
Operating profit
NOK 105.8m
Equity
NOK 76.8m
Est. value
NOK 275.9m

Financial health · 2024

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

Who owns SKÅRER BOLIG AS?

SELVAAG BOLIG ASA
SKÅRER BOLIG AS
NOK 774.1m rev. · NOK 105.8m profit

SKÅRER BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKÅRER BOLIG AS

Who owns SKÅRER BOLIG AS?

SELVAAG BOLIG ASA is the largest registered owner, with 100.0%.

What is the revenue of SKÅRER BOLIG AS?

SKÅRER BOLIG AS had revenue of NOK 774.1m in 2024.

Where is SKÅRER BOLIG AS based?

SKÅRER BOLIG AS has its business address in Oslo.

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.