biztrac. BETA
COMPANY REGISTER PROFILE
982170931 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HELLERUDVEIEN EIENDOM AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Development of building projects

HELLERUDVEIEN EIENDOM AS

Org. no. 982170931 Limited company (AS) Bærum Incorporated 2000 In liquidation
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 151,000
Incorporated 2000
Share capital NOK 100,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−27k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HELLERUDVEIEN EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 982170931. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverv, utvikling og salg av eiendommen Hellerudveien 2 (gnr. 112 bnr. 17) i Bærum kommune.”.

Key figures · 2025

Operating profit
NOK −27,000
▼ −120 %
Equity
NOK 151,000
▼ −11 %

Financial health · 2025

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

Who owns HELLERUDVEIEN EIENDOM AS?

HELLERUDVEIEN EIENDOM AS
· NOK −27,000 profit

HELLERUDVEIEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELLERUDVEIEN EIENDOM AS

Who owns HELLERUDVEIEN EIENDOM AS?

BACKE PROSJEKT AS is the largest registered owner, with 98.0%.

Where is HELLERUDVEIEN EIENDOM AS based?

HELLERUDVEIEN EIENDOM AS has its business address in Lysaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.