BIZTRAC BETA
Rental and operating of own or leased real estate

M.I.E HOLDING AS

Org. no. 930219002 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 22,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

M.I.E HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 930219002. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i andre bedrifter. Kjøp, salg og utleie av eiendom. Kjøp og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 22,000
Est. value
NOK 20,000

Financial health · 2025

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

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

Who owns M.I.E HOLDING AS?

LEIF-ØIVIND EDSTRØM
M.I.E HOLDING AS
NOK 0 rev. · NOK −4,000 profit

M.I.E HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M.I.E HOLDING AS

Who owns M.I.E HOLDING AS?

LEIF-ØIVIND EDSTRØM is the largest registered owner, with 100.0%.

What is the revenue of M.I.E HOLDING AS?

M.I.E HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of M.I.E HOLDING AS?

Leif-Øivind Edstrøm is registered as general manager of M.I.E HOLDING AS.

Where is M.I.E HOLDING AS based?

M.I.E HOLDING AS has its business address in Moss.

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.