biztrac. BETA
COMPANY REGISTER PROFILE
927473321 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MHW INVEST AS

Org. no. 927473321 Limited company (AS) Bærum Incorporated 2021 Active
Revenue 2025 NOK 343,000
Operating profit NOK 261,000
Equity NOK 12.2m
Incorporated 2021
Share capital NOK 30,000

MHW INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 927473321. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap som skal drive med investeringer innenfor eiendom og aksjer (noterte og unoterte).”. The most recent filed accounts, for the 2025 financial year, show NOK 343,000 in revenue and NOK 261,000 in operating profit.

Key figures · 2025

Revenue
NOK 343,000
Operating profit
NOK 261,000
▲ +6155 %
Equity
NOK 12.2m
▲ +4033 %
Est. value
NOK 7.2m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
174.8%
Very good
Return on total assets
Solidity
94.6%
Very good
Equity as a share of total capital

Who owns MHW INVEST AS?

MHW INVEST AS
NOK 343,000 rev. · NOK 261,000 profit

MHW INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MHW INVEST AS own?

MHW INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MHW INVEST AS

Who owns MHW INVEST AS?

Mehdi Hashemi-Wictorin is the largest registered owner, with 100.0%.

What is the revenue of MHW INVEST AS?

MHW INVEST AS had revenue of NOK 343,000 in 2025.

Who is the general manager of MHW INVEST AS?

Mehdi Hashemi-Wictorin is registered as general manager of MHW INVEST AS.

Where is MHW INVEST AS based?

MHW INVEST AS has its business address in Fornebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.