BIZTRAC BETA
Rental and operating of own or leased real estate

HEGDEHAUGSVEIEN 25 BOLIG AS

Org. no. 999019943 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 533,000
Equity NOK 9.2m
Incorporated 2012
Share capital NOK 108,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 25 BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 999019943. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 108,000, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 533,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 533,000
Equity
NOK 9.2m
Est. value
NOK 7.4m

Financial health · 2024

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.6%
Very good
Equity as a share of total capital

Who owns HEGDEHAUGSVEIEN 25 BOLIG AS?

HCH EIENDOM AS
HEGDEHAUGSVEIEN 25 BOLIG AS
NOK 1.7m rev. · NOK 533,000 profit

HEGDEHAUGSVEIEN 25 BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEGDEHAUGSVEIEN 25 BOLIG AS

Who owns HEGDEHAUGSVEIEN 25 BOLIG AS?

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

What is the revenue of HEGDEHAUGSVEIEN 25 BOLIG AS?

HEGDEHAUGSVEIEN 25 BOLIG AS had revenue of NOK 1.7m in 2024.

Where is HEGDEHAUGSVEIEN 25 BOLIG AS based?

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