BIZTRAC BETA
Research and experimental development on natural sciences and engineering

REN POWER AS

Org. no. 928692639 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −147,000
Equity NOK −105,000
Incorporated 2022
Share capital NOK 365,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−105k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−147k kr).

REN POWER AS is registered as a limited company in Bærum, Akershus with organisation number 928692639. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2022. Registered share capital is NOK 365,000, divided into 365000 shares. The company's stated purpose is: “Å utvikle, investere i, bygge og finansiere løsninger innenfor ren og fornybar energi gjennom eierskap av teknologiselskaper, prosjekt og driftsselskaper, fysiske energianlegg samt ulike finansielle instrumenter og annen virksomhet som står i naturlig forhold til dette.”.

Key figures · 2025

Operating profit
NOK −147,000
Equity
NOK −105,000

Financial health · 2025

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

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

Who owns REN POWER AS?

FAMBO INVEST AS
REN POWER AS
· NOK −147,000 profit

REN POWER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REN POWER AS

Who owns REN POWER AS?

FAMBO INVEST AS is the largest registered owner, with 50.0%.

Who is the general manager of REN POWER AS?

Tore Borthen is registered as general manager of REN POWER AS.

Where is REN POWER AS based?

REN POWER AS has its business address in Høvik.

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.