BIZTRAC BETA
Rental and operating of own or leased real estate

NYE HEGDEHAUGSVEIEN 21 AS

Org. no. 819367272 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 10.0m
Operating profit NOK 6.4m
Equity NOK 14.7m
Incorporated 2017
Share capital NOK 40,000

Signals

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

NYE HEGDEHAUGSVEIEN 21 AS is registered as a limited company in Oslo, Oslo with organisation number 819367272. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 1 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 2025 financial year, show NOK 10.0m in revenue and NOK 6.4m in operating profit.

Key figures · 2025

Revenue
NOK 10.0m
Operating profit
NOK 6.4m
Equity
NOK 14.7m
Est. value
NOK 22.8m

Financial health · 2025

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

Who owns NYE HEGDEHAUGSVEIEN 21 AS?

AABERG EIENDOM AS
NYE HEGDEHAUGSVEIEN 21 AS
NOK 10.0m rev. · NOK 6.4m profit

NYE HEGDEHAUGSVEIEN 21 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYE HEGDEHAUGSVEIEN 21 AS

Who owns NYE HEGDEHAUGSVEIEN 21 AS?

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

What is the revenue of NYE HEGDEHAUGSVEIEN 21 AS?

NYE HEGDEHAUGSVEIEN 21 AS had revenue of NOK 10.0m in 2025.

Where is NYE HEGDEHAUGSVEIEN 21 AS based?

NYE HEGDEHAUGSVEIEN 21 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.