BIZTRAC BETA
Rental and operating of own or leased real estate

MALERHAUGVEIEN BOLIG AS

Org. no. 931048023 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 5.1m
Equity NOK 13.7m
Incorporated 2023
Share capital NOK 1.5m

Signals

1 flags
  • Nylig endring 2026-03-23 Aksjekapital registrert 2026-03-23.

MALERHAUGVEIEN BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 931048023. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 1.5m, divided into 5000 shares. The company's stated purpose is: “Eie, forvalte og leie ut boliger, samt øvrig investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 5.1m in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK 5.1m
Equity
NOK 13.7m
Est. value
NOK 17.0m

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns MALERHAUGVEIEN BOLIG AS?

LILLE OSLO EIENDOM AS
MALERHAUGVEIEN BOLIG AS
NOK 8.8m rev. · NOK 5.1m profit

MALERHAUGVEIEN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MALERHAUGVEIEN BOLIG AS

Who owns MALERHAUGVEIEN BOLIG AS?

LILLE OSLO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MALERHAUGVEIEN BOLIG AS?

MALERHAUGVEIEN BOLIG AS had revenue of NOK 8.8m in 2025.

Who is the general manager of MALERHAUGVEIEN BOLIG AS?

Hilde Vik Matre is registered as general manager of MALERHAUGVEIEN BOLIG AS.

Where is MALERHAUGVEIEN BOLIG AS based?

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