BIZTRAC BETA
Other captive investment companies

MIDAT INVEST AS

Org. no. 833900242 Limited company (AS) Tromsø Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1,000
Equity NOK 133,000
Incorporated 1983
Share capital NOK 100,000

Signals

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

MIDAT INVEST AS is registered as a limited company in Tromsø, Troms with organisation number 833900242. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1983. Registered share capital is NOK 100,000. The company's stated purpose is: “Drive industri, handel og hva hermed står i forbindelse, herunder å delta i andre selskaper med slikt formål og å eie og forvalte verdipapirer og andre formuesgjenstander.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 133,000
Est. value
NOK 121,000

Financial health · 2024

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

Who owns MIDAT INVEST AS?

No shareholders are registered for MIDAT INVEST AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does MIDAT INVEST AS own?

MIDAT INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MIDAT INVEST AS

What is the revenue of MIDAT INVEST AS?

MIDAT INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of MIDAT INVEST AS?

Kjell Bjørnar Mortensen is registered as general manager of MIDAT INVEST AS.

Where is MIDAT INVEST AS based?

MIDAT INVEST AS has its business address in Kvaløysletta.

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.