BIZTRAC BETA
Other specialised construction activities n.e.c.

MPENERGI AS

Org. no. 916574347 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 267,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 230,000

MPENERGI AS is registered as a limited company in Oslo, Oslo with organisation number 916574347. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2015. Registered share capital is NOK 230,000, divided into 2300 shares. The company's stated purpose is: “Annen spesialisert bygge - og anleggsvirksomhet : Prosjekt og konsulent tjenester. Fornybar energi. Energi effektivisering Klima og miljø. Maritime tjenester over og under vann. Herunder alt som står i de nevntes formål forbindelser nasjonalt og internasjonalt.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 267,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 267,000
Equity
NOK 1.1m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns MPENERGI AS?

MPENERGY INTERNATIONAL LTD NUF
MPENERGI AS
NOK 2.6m rev. · NOK 267,000 profit

MPENERGI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MPENERGI AS

Who owns MPENERGI AS?

MPENERGY INTERNATIONAL LTD NUF is the largest registered owner, with 100.0%.

What is the revenue of MPENERGI AS?

MPENERGI AS had revenue of NOK 2.6m in 2025.

Who is the general manager of MPENERGI AS?

Morten Pedersen is registered as general manager of MPENERGI AS.

Where is MPENERGI AS based?

MPENERGI 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.