BIZTRAC BETA
Production of electricity from hydropower

LOCUS HOLDCO AS

Org. no. 932902869 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK 30,000
Incorporated 2024
Share capital NOK 31,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-26 Adresseendring registrert 2026-03-26.

LOCUS HOLDCO AS is registered as a limited company in Oslo, Oslo with organisation number 932902869. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2024. Registered share capital is NOK 31,000, divided into 3100 shares. The company's stated purpose is: “Å eie, drive og utvikle vannkraftverk i Norge samt virksomhet som står i naturlig sammenheng med dette. Virksomheten kan drives alene, i samarbeid med andre eller ved deltagelse i andre foretak.”.

Key figures · 2024

Operating profit
NOK −44,000
Equity
NOK 30,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

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

Who owns LOCUS HOLDCO AS?

LOCUS ENERGY AB
LOCUS HOLDCO AS
· NOK −44,000 profit

LOCUS HOLDCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOCUS HOLDCO AS own?

LOCUS HOLDCO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LOCUS HOLDCO AS

Who owns LOCUS HOLDCO AS?

LOCUS ENERGY AB is the largest registered owner, with 100.0%.

Where is LOCUS HOLDCO AS based?

LOCUS HOLDCO 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.