BIZTRAC BETA
Rental and operating of own or leased real estate

M.MITHASSEL HOLDING AS

Org. no. 922153140 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 2.0m
Incorporated 2019
Share capital NOK 30,000

Signals

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

M.MITHASSEL HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 922153140. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drive fast eiendom samt verdipapirer og deltagelse i andre selvskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 2.0m
Est. value
NOK 10.3m

Financial health · 2025

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

Who owns M.MITHASSEL HOLDING AS?

MARIUS MOBERG MITHASSEL
M.MITHASSEL HOLDING AS
NOK 0 rev. · NOK −19,000 profit

M.MITHASSEL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M.MITHASSEL HOLDING AS own?

M.MITHASSEL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about M.MITHASSEL HOLDING AS

Who owns M.MITHASSEL HOLDING AS?

MARIUS MOBERG MITHASSEL is the largest registered owner, with 100.0%.

What is the revenue of M.MITHASSEL HOLDING AS?

M.MITHASSEL HOLDING AS had revenue of NOK 0 in 2025.

Where is M.MITHASSEL HOLDING AS based?

M.MITHASSEL HOLDING 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.