BIZTRAC BETA
Uoppgitt

IHLEBÆK HOLDING AS

Org. no. 933916553 Limited company (AS) Færder Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 399
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

IHLEBÆK HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 933916553. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i andre virksomheter og fast eiendom. Herunder kjøp, salg og utleie av fast eiendom samt kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 399
Est. value
NOK 469

Financial health · 2025

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

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

Who owns IHLEBÆK HOLDING AS?

MARTIN JOHANSEN IHLEBÆK
IHLEBÆK HOLDING AS
NOK 0 rev. · NOK −18,000 profit

IHLEBÆK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IHLEBÆK HOLDING AS own?

IHLEBÆK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IHLEBÆK HOLDING AS

Who owns IHLEBÆK HOLDING AS?

MARTIN JOHANSEN IHLEBÆK is the largest registered owner, with 100.0%.

What is the revenue of IHLEBÆK HOLDING AS?

IHLEBÆK HOLDING AS had revenue of NOK 0 in 2025.

Where is IHLEBÆK HOLDING AS based?

IHLEBÆK HOLDING AS has its business address in Nøtterøy.

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.