BIZTRAC BETA
Rental and operating of own or leased real estate

IHLEBÆK EIENDOM AS

Org. no. 933498298 Limited company (AS) Frogn Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 220,000
Operating profit NOK −52,000
Equity NOK 29.9m
Incorporated 2024
Share capital NOK 685,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−52k kr).

IHLEBÆK EIENDOM AS is registered as a limited company in Frogn, Akershus with organisation number 933498298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 685,000, divided into 684578 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt kjøp og salg av aksjer og andre finansinvesteringer og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 220,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2024

Revenue
NOK 220,000
Operating profit
NOK −52,000
Equity
NOK 29.9m
Est. value
NOK 20.8m

Financial health · 2024

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

Who owns IHLEBÆK EIENDOM AS?

OSCAR ANDREAS IHLEBÆK
IHLEBÆK EIENDOM AS
NOK 220,000 rev. · NOK −52,000 profit

IHLEBÆK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IHLEBÆK EIENDOM AS

Who owns IHLEBÆK EIENDOM AS?

OSCAR ANDREAS IHLEBÆK is the largest registered owner, with 100.0%.

What is the revenue of IHLEBÆK EIENDOM AS?

IHLEBÆK EIENDOM AS had revenue of NOK 220,000 in 2024.

Where is IHLEBÆK EIENDOM AS based?

IHLEBÆK EIENDOM AS has its business address in Drøbak.

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.