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

MUH HOLDING AS

Org. no. 927955342 Limited company (AS) Bergen Incorporated 2021 Active
Operating profit NOK −1,000
Equity NOK 9,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

MUH HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927955342. 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: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −1,000
▲ +93 %
Equity
NOK 9,000
▼ −13 %
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns MUH HOLDING AS?

MUH HOLDING AS
· NOK −1,000 profit

MUH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUH HOLDING AS own?

MUH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MUH HOLDING AS

Who owns MUH HOLDING AS?

Marius Undheim Helvik is the largest registered owner, with 100.0%.

Who is the general manager of MUH HOLDING AS?

Marius Undheim Helvik is registered as general manager of MUH HOLDING AS.

Where is MUH HOLDING AS based?

MUH HOLDING AS has its business address in Bergen.

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.