BIZTRAC BETA
Production of electricity from wind power

MARKER VINDPARK AS

Org. no. 915592163 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 6.4m
Operating profit NOK 183,000
Equity NOK 5.2m
Incorporated 2015
Share capital NOK 1.0m

MARKER VINDPARK AS is registered as a limited company in Oslo, Oslo with organisation number 915592163. The business is classified under production of electricity from wind power (NACE 35.122). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 34333 shares. The company's stated purpose is: “Investeringer i vindkraftparker og verdipapirer for å utnytte, produsere, distribuere og omsette energi samt annen virksomhet i tilknytning til dette, herunder deltakelse i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.4m in revenue and NOK 183,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.4m
Operating profit
NOK 183,000
Equity
NOK 5.2m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns MARKER VINDPARK AS?

BKW RENEWABLES PARTNERS AG
MARKER VINDPARK AS
NOK 6.4m rev. · NOK 183,000 profit

MARKER VINDPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARKER VINDPARK AS

Who owns MARKER VINDPARK AS?

BKW RENEWABLES PARTNERS AG is the largest registered owner, with 100.0%.

What is the revenue of MARKER VINDPARK AS?

MARKER VINDPARK AS had revenue of NOK 6.4m in 2024.

Who is the general manager of MARKER VINDPARK AS?

Joakim Onarheim Martens is registered as general manager of MARKER VINDPARK AS.

Where is MARKER VINDPARK AS based?

MARKER VINDPARK 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.