BIZTRAC BETA
Other real estate activities on a fee or contract basis

BOLIGFORVALTNING AS

Org. no. 916449798 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 14.6m
Operating profit NOK −22.1m
Equity NOK 2.9m
Incorporated 2015
Share capital NOK 30,000

Signals

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

BOLIGFORVALTNING AS is registered as a limited company in Oslo, Oslo with organisation number 916449798. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Forvaltning og drift av fast eiendom og alt som hører dertil.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.6m in revenue and NOK −22.1m in operating profit.

Key figures · 2024

Revenue
NOK 14.6m
Operating profit
NOK −22.1m
Equity
NOK 2.9m
Est. value
NOK 23.9m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns BOLIGFORVALTNING AS?

SELVAAG UTLEIEBOLIG AS
BOLIGFORVALTNING AS
NOK 14.6m rev. · NOK −22.1m profit

BOLIGFORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGFORVALTNING AS

Who owns BOLIGFORVALTNING AS?

SELVAAG UTLEIEBOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of BOLIGFORVALTNING AS?

BOLIGFORVALTNING AS had revenue of NOK 14.6m in 2024.

Where is BOLIGFORVALTNING AS based?

BOLIGFORVALTNING 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.