BIZTRAC BETA
Other captive investment companies

MORTEN HIPPE HOLDING AS

Org. no. 917091439 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 103,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

MORTEN HIPPE HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 917091439. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive investering i aksjer og verdipapirer og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 103,000
Est. value
NOK 94,000

Financial health · 2025

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

Who owns MORTEN HIPPE HOLDING AS?

MORTEN HIPPE
MORTEN HIPPE HOLDING AS
NOK 0 rev. · NOK −9,000 profit

MORTEN HIPPE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MORTEN HIPPE HOLDING AS own?

MORTEN HIPPE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MORTEN HIPPE HOLDING AS

Who owns MORTEN HIPPE HOLDING AS?

MORTEN HIPPE is the largest registered owner, with 100.0%.

What is the revenue of MORTEN HIPPE HOLDING AS?

MORTEN HIPPE HOLDING AS had revenue of NOK 0 in 2025.

Where is MORTEN HIPPE HOLDING AS based?

MORTEN HIPPE HOLDING AS has its business address in Jar.

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.