BIZTRAC BETA
Other captive investment companies

MORTEN RØNNING HOLDING AS

Org. no. 914461294 Limited company (AS) Kristiansand Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −99,000
Equity NOK 548,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

MORTEN RØNNING HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 914461294. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å eie aksjer og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −99,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −99,000
Equity
NOK 548,000
Est. value
NOK 312,000

Financial health · 2024

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

Who owns MORTEN RØNNING HOLDING AS?

MORTEN RØNNING
MORTEN RØNNING HOLDING AS
NOK 0 rev. · NOK −99,000 profit

MORTEN RØNNING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MORTEN RØNNING HOLDING AS own?

MORTEN RØNNING HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MORTEN RØNNING HOLDING AS

Who owns MORTEN RØNNING HOLDING AS?

MORTEN RØNNING is the largest registered owner, with 100.0%.

What is the revenue of MORTEN RØNNING HOLDING AS?

MORTEN RØNNING HOLDING AS had revenue of NOK 0 in 2024.

Where is MORTEN RØNNING HOLDING AS based?

MORTEN RØNNING HOLDING AS has its business address in Kristiansand S.

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.