BIZTRAC BETA
Uoppgitt

MIDI INVEST AS

Org. no. 927319640 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 3,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

MIDI INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 927319640. 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: “Forvaltning av eierinteresser, herunder aksjer, eiendom m.m., og det som måtte stå i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 3,000
Est. value
NOK 3,000

Financial health · 2025

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

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

Who owns MIDI INVEST AS?

MAGNUS BJELLAND
MIDI INVEST AS
NOK 0 rev. · NOK −5,000 profit

MIDI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIDI INVEST AS own?

MIDI INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MIDI INVEST AS

Who owns MIDI INVEST AS?

MAGNUS BJELLAND is the largest registered owner, with 100.0%.

What is the revenue of MIDI INVEST AS?

MIDI INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of MIDI INVEST AS?

Magnus Bjelland is registered as general manager of MIDI INVEST AS.

Where is MIDI INVEST AS based?

MIDI INVEST 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.