BIZTRAC BETA
Trade of electricity

VIBB AS

Org. no. 919439734 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 888.2m
Operating profit NOK −47.8m
Equity NOK 67.2m
Incorporated 2017
Employees 24
Share capital NOK 22.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47,8 mill kr).

VIBB AS is registered as a limited company in Drammen, Buskerud with organisation number 919439734. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 2017 and has 24 registered employees. Registered share capital is NOK 22.0m, divided into 2000 shares. The company's stated purpose is: “Eie og drive sluttbrukersalg innenfor strøm og strømrelaterte tjenester, herunder tjenester knyttet til måling, automasjon og porteføljestyring.”. The most recent filed accounts, for the 2024 financial year, show NOK 888.2m in revenue and NOK −47.8m in operating profit.

Key figures · 2024

Revenue
NOK 888.2m
Operating profit
NOK −47.8m
Equity
NOK 67.2m
Est. value
NOK 710.5m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.0%
Good
Equity as a share of total capital

Who owns VIBB AS?

Å ENERGI AS
VIBB AS
NOK 888.2m rev. · NOK −47.8m profit

VIBB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIBB AS own?

VIBB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIBB AS

Who owns VIBB AS?

Å ENERGI AS is the largest registered owner, with 100.0%.

What is the revenue of VIBB AS?

VIBB AS had revenue of NOK 888.2m in 2024.

Who is the general manager of VIBB AS?

Erik Berg Solheim is registered as general manager of VIBB AS.

Where is VIBB AS based?

VIBB AS has its business address in Drammen.

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.