BIZTRAC BETA
Other software publishing

MPOWER AS

Org. no. 984585020 Limited company (AS) Tromsø Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −64,000
Equity NOK 1.0m
Incorporated 2002
Share capital NOK 217,000

Signals

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

MPOWER AS is registered as a limited company in Tromsø, Troms with organisation number 984585020. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2002. Registered share capital is NOK 217,000, divided into 217000 shares. The company's stated purpose is: “Utvikling, markedsføring og salg av IKT-løsninger for mobile nett, og dertil hørende virksomhet. Selskapet kan delta i andre virksomheter som understøtter slike forretningsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −64,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −64,000
Equity
NOK 1.0m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns MPOWER AS?

WIGGO FINNSET
MPOWER AS
NOK 1.1m rev. · NOK −64,000 profit

MPOWER AS has 14 registered shareholders:

All shareholders and roles →

Which companies does MPOWER AS own?

MPOWER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MPOWER AS

Who owns MPOWER AS?

WIGGO FINNSET is the largest registered owner, with 24.1%.

What is the revenue of MPOWER AS?

MPOWER AS had revenue of NOK 1.1m in 2024.

Who is the general manager of MPOWER AS?

Wiggo Finnset is registered as general manager of MPOWER AS.

Where is MPOWER AS based?

MPOWER AS has its business address in Tromsø.

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.