BIZTRAC BETA
Development of building projects

SELVAAG BOLIG LANDÅS AS

Org. no. 996834859 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK −5.7m
Equity NOK 17.1m
Incorporated 2011
Share capital NOK 52,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,7 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SELVAAG BOLIG LANDÅS AS is registered as a limited company in Oslo, Oslo with organisation number 996834859. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 52,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er eiendomsutvikling samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK −5.7m in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK −5.7m
Equity
NOK 17.1m
Est. value
NOK 15.6m

Financial health · 2024

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

Who owns SELVAAG BOLIG LANDÅS AS?

SELVAAG BOLIG ASA
SELVAAG BOLIG LANDÅS AS
NOK 15.8m rev. · NOK −5.7m profit

SELVAAG BOLIG LANDÅS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELVAAG BOLIG LANDÅS AS

Who owns SELVAAG BOLIG LANDÅS AS?

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

What is the revenue of SELVAAG BOLIG LANDÅS AS?

SELVAAG BOLIG LANDÅS AS had revenue of NOK 15.8m in 2024.

Where is SELVAAG BOLIG LANDÅS AS based?

SELVAAG BOLIG LANDÅS 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.