BIZTRAC BETA
Rental and operating of own or leased real estate

HEGDEHAUGSVEIEN 32 AS

Org. no. 917865884 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 3.5m
Equity NOK 304,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

HEGDEHAUGSVEIEN 32 AS is registered as a limited company in Oslo, Oslo with organisation number 917865884. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utvikling og forvaltning av eiendom, samt hva som hermed står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 3.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 3.5m
Equity
NOK 304,000
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns HEGDEHAUGSVEIEN 32 AS?

MB PROPERTY 1 AS
HEGDEHAUGSVEIEN 32 AS
NOK 7.2m rev. · NOK 3.5m profit

HEGDEHAUGSVEIEN 32 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEGDEHAUGSVEIEN 32 AS

Who owns HEGDEHAUGSVEIEN 32 AS?

MB PROPERTY 1 AS is the largest registered owner, with 100.0%.

What is the revenue of HEGDEHAUGSVEIEN 32 AS?

HEGDEHAUGSVEIEN 32 AS had revenue of NOK 7.2m in 2024.

Where is HEGDEHAUGSVEIEN 32 AS based?

HEGDEHAUGSVEIEN 32 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.