BIZTRAC BETA
Rental and operating of own or leased real estate

HÅBAKKEN EIGEDOM AS

Org. no. 915363385 Limited company (AS) Lærdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 450,000
Equity NOK −1.1m
Incorporated 2015
Share capital NOK 90,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Nylig endring 2026-02-13 Adresseendring registrert 2026-02-13.

HÅBAKKEN EIGEDOM AS is registered as a limited company in Lærdal, Vestland with organisation number 915363385. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 90,000, divided into 900 shares. The company's stated purpose is: “Å eie, utvikle og forvalte fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 450,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 450,000
Equity
NOK −1.1m
Est. value
NOK 3.1m

Financial health · 2024

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

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

Who owns HÅBAKKEN EIGEDOM AS?

LOKREIM HOLDING AS
HÅBAKKEN EIGEDOM AS
NOK 1.2m rev. · NOK 450,000 profit

HÅBAKKEN EIGEDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HÅBAKKEN EIGEDOM AS

Who owns HÅBAKKEN EIGEDOM AS?

LOKREIM HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of HÅBAKKEN EIGEDOM AS?

HÅBAKKEN EIGEDOM AS had revenue of NOK 1.2m in 2024.

Where is HÅBAKKEN EIGEDOM AS based?

HÅBAKKEN EIGEDOM AS has its business address in Lærdal.

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.