BIZTRAC BETA
Other software publishing

MI PRO AS

Org. no. 982467632 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK −194,000
Equity NOK 782,000
Incorporated 2000
Share capital NOK 223,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−194k kr).
  • Nylig endring 2026-06-01 Adresseendring registrert 2026-06-01.

MI PRO AS is registered as a limited company in Oslo, Oslo with organisation number 982467632. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2000. Registered share capital is NOK 223,000, divided into 2227500 shares. The company's stated purpose is: “Utvikling- og salg av informasjonssystem, konsulentvirksomhet innenfor IT-bransjen, samt ved innskudd eller på annen måte ta økonomisk del i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK −194,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK −194,000
Equity
NOK 782,000
Est. value
NOK 10.2m

Financial health · 2025

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.0%
Very good
Equity as a share of total capital

Who owns MI PRO AS?

PÅL SESSENG
MI PRO AS
NOK 5.8m rev. · NOK −194,000 profit

MI PRO AS has 2 registered shareholders:

All shareholders and roles →

Group structure

MI PRO AS er morselskap for 2 datterselskaper:

Frequently asked questions about MI PRO AS

Who owns MI PRO AS?

PÅL SESSENG is the largest registered owner, with 50.0%.

What is the revenue of MI PRO AS?

MI PRO AS had revenue of NOK 5.8m in 2025.

Who is the general manager of MI PRO AS?

Pål Sesseng is registered as general manager of MI PRO AS.

Where is MI PRO AS based?

MI PRO 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.