BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

LISTA RENEWABLE ENERGY PARK HOLDING AS

Org. no. 919424036 Limited company (AS) Farsund Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK 8.0m
Incorporated 2017
Share capital NOK 531,000

Signals

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

LISTA RENEWABLE ENERGY PARK HOLDING AS is registered as a limited company in Farsund, Agder with organisation number 919424036. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2017. Registered share capital is NOK 531,000, divided into 1000 shares. The company's stated purpose is: “Investeringer og deltakelse i andre selskaper og eiendom, samt alt som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −30,000
Equity
NOK 8.0m
Est. value
NOK 14.6m

Financial health · 2025

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

Who owns LISTA RENEWABLE ENERGY PARK HOLDING AS?

LISTA REAL AS
LISTA RENEWABLE ENERGY PARK HOLDING AS
· NOK −30,000 profit

LISTA RENEWABLE ENERGY PARK HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LISTA RENEWABLE ENERGY PARK HOLDING AS own?

LISTA RENEWABLE ENERGY PARK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LISTA RENEWABLE ENERGY PARK HOLDING AS

Who owns LISTA RENEWABLE ENERGY PARK HOLDING AS?

LISTA REAL AS is the largest registered owner, with 40.0%.

Where is LISTA RENEWABLE ENERGY PARK HOLDING AS based?

LISTA RENEWABLE ENERGY PARK HOLDING AS has its business address in Vanse.

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.