BIZTRAC BETA
Other captive investment companies

MB INVESTERINGER AS

Org. no. 991919511 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 35,000
Operating profit NOK −37,000
Equity NOK 13,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

MB INVESTERINGER AS is registered as a limited company in Asker, Akershus with organisation number 991919511. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 35,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 35,000
Operating profit
NOK −37,000
Equity
NOK 13,000
Est. value
NOK 12,000

Financial health · 2024

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

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

Who owns MB INVESTERINGER AS?

TORE BERGAN
MB INVESTERINGER AS
NOK 35,000 rev. · NOK −37,000 profit

MB INVESTERINGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MB INVESTERINGER AS own?

MB INVESTERINGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MB INVESTERINGER AS

Who owns MB INVESTERINGER AS?

TORE BERGAN is the largest registered owner, with 100.0%.

What is the revenue of MB INVESTERINGER AS?

MB INVESTERINGER AS had revenue of NOK 35,000 in 2024.

Where is MB INVESTERINGER AS based?

MB INVESTERINGER AS has its business address in Borgen.

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.