BIZTRAC BETA
Wholesale of hardware, plumbing and heating equipment and supplies

OSO ENERGY AS

Org. no. 925156663 Limited company (AS) Øvre Eiker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 9,000
Operating profit NOK −1.0m
Equity NOK 6.0m
Incorporated 2020
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,0 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OSO ENERGY AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 925156663. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 2020. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Markedsføring, distribusjon og salg av varmtvannsberedere med digitale styringssystemer og tilhørende tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 9,000 in revenue and NOK −1.0m in operating profit.

Key figures · 2024

Revenue
NOK 9,000
Operating profit
NOK −1.0m
Equity
NOK 6.0m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns OSO ENERGY AS?

OSO GROUP AS
OSO ENERGY AS
NOK 9,000 rev. · NOK −1.0m profit

OSO ENERGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSO ENERGY AS

Who owns OSO ENERGY AS?

OSO GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of OSO ENERGY AS?

OSO ENERGY AS had revenue of NOK 9,000 in 2024.

Where is OSO ENERGY AS based?

OSO ENERGY AS has its business address in Hokksund.

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.