BIZTRAC BETA
Construction of utility projects for electricity and telecommunications on land

VOLUND POWER AS

Org. no. 931458817 Limited company (AS) Ringerike Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −150,000
Equity NOK −126,000
Incorporated 2023
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−126k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−150k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VOLUND POWER AS is registered as a limited company in Ringerike, Buskerud with organisation number 931458817. The business is classified under construction of utility projects for electricity and telecommunications on land (NACE 42.222). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive entreprenør- og rådgivningstjenester innen EPC, samt annen virksomhet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −150,000
Equity
NOK −126,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1449.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VOLUND POWER AS?

LAJE AS
VOLUND POWER AS
· NOK −150,000 profit

VOLUND POWER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOLUND POWER AS

Who owns VOLUND POWER AS?

LAJE AS is the largest registered owner, with 51.0%.

Who is the general manager of VOLUND POWER AS?

Eirik Grønlund is registered as general manager of VOLUND POWER AS.

Where is VOLUND POWER AS based?

VOLUND POWER AS has its business address in Hønefoss.

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.