BIZTRAC BETA
Other captive investment companies

MBU INVEST AS

Org. no. 916342985 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.7m
Equity NOK 6.3m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

MBU INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 916342985. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andelser i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.7m
Equity
NOK 6.3m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns MBU INVEST AS?

MARIANNE BRUSDAL
MBU INVEST AS
NOK 1.8m rev. · NOK 1.7m profit

MBU INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MBU INVEST AS own?

MBU INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MBU INVEST AS

Who owns MBU INVEST AS?

MARIANNE BRUSDAL is the largest registered owner, with 100.0%.

What is the revenue of MBU INVEST AS?

MBU INVEST AS had revenue of NOK 1.8m in 2025.

Who is the general manager of MBU INVEST AS?

Marianne Brusdal is registered as general manager of MBU INVEST AS.

Where is MBU INVEST AS based?

MBU INVEST AS has its business address in Oslo.

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.