BIZTRAC BETA
Other captive investment companies

MH-HOLDING AS

Org. no. 920033946 Limited company (AS) Sør-Odal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 1.4m
Incorporated 2017
Share capital NOK 30,000

Signals

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

MH-HOLDING AS is registered as a limited company in Sør-Odal, Innlandet with organisation number 920033946. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Kjøp, salg og forvaltning av aksjer, øvrige verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 1.4m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns MH-HOLDING AS?

MARTIN BREIBY HOLTH
MH-HOLDING AS
NOK 0 rev. · NOK −29,000 profit

MH-HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MH-HOLDING AS own?

MH-HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MH-HOLDING AS

Who owns MH-HOLDING AS?

MARTIN BREIBY HOLTH is the largest registered owner, with 100.0%.

What is the revenue of MH-HOLDING AS?

MH-HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of MH-HOLDING AS?

Martin Breiby Holth is registered as general manager of MH-HOLDING AS.

Where is MH-HOLDING AS based?

MH-HOLDING AS has its business address in Skarnes.

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.