BIZTRAC BETA
Development of building projects

HEGGALLEEN EIENDOM AS

Org. no. 916377215 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −34,000
Equity NOK −232,000
Incorporated 2015
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−232k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEGGALLEEN EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 916377215. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Prosjekt- og eiendomsutvikling, samt deltagelse i andre selskaper og annet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −34,000
Equity
NOK −232,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-53964.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HEGGALLEEN EIENDOM AS?

GLITRE BOLIG AS
HEGGALLEEN EIENDOM AS
· NOK −34,000 profit

HEGGALLEEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEGGALLEEN EIENDOM AS

Who owns HEGGALLEEN EIENDOM AS?

GLITRE BOLIG AS is the largest registered owner, with 100.0%.

Who is the general manager of HEGGALLEEN EIENDOM AS?

Morten Corneliussen is registered as general manager of HEGGALLEEN EIENDOM AS.

Where is HEGGALLEEN EIENDOM AS based?

HEGGALLEEN EIENDOM AS has its business address in Drammen.

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.