BIZTRAC BETA
Rental and operating of own or leased real estate

ENEBAKK EIENDOMSINVEST AS

Org. no. 926420178 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −335,000
Equity NOK 26.3m
Incorporated 2021
Share capital NOK 70,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−335k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ENEBAKK EIENDOMSINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 926420178. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 70,000, divided into 35000 shares. The company's stated purpose is: “Utvikling, forvaltning og investering i andre selskaper, samt investering i fast eiendom og andre formuesgoder og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2024

Operating profit
NOK −335,000
Equity
NOK 26.3m
Est. value
NOK 22.4m

Financial health · 2024

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.4%
Good
Equity as a share of total capital

Who owns ENEBAKK EIENDOMSINVEST AS?

KRAFT EIENDOMSINVEST I AS
ENEBAKK EIENDOMSINVEST AS
· NOK −335,000 profit

ENEBAKK EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENEBAKK EIENDOMSINVEST AS own?

ENEBAKK EIENDOMSINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENEBAKK EIENDOMSINVEST AS

Who owns ENEBAKK EIENDOMSINVEST AS?

KRAFT EIENDOMSINVEST I AS is the largest registered owner, with 100.0%.

Where is ENEBAKK EIENDOMSINVEST AS based?

ENEBAKK EIENDOMSINVEST 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.