BIZTRAC BETA
Computer consultancy and computer facilities management activities

VOLUE AS

Org. no. 924332166 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 61.4m
Operating profit NOK −35.9m
Equity NOK 4.7bn
Incorporated 2019
Share capital NOK 59.0m

Signals

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

VOLUE AS is registered as a limited company in Oslo, Oslo with organisation number 924332166. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 59.0m, divided into 143853375 shares. The company's stated purpose is: “Å investere i, eie og forvalte selskaper, samt drive egen virksomhet innen IT og annen software og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.4m in revenue and NOK −35.9m in operating profit.

Key figures · 2024

Revenue
NOK 61.4m
Operating profit
NOK −35.9m
Equity
NOK 4.7bn
Est. value
NOK 17.0bn

Financial health · 2024

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
89.4%
Very good
Equity as a share of total capital

Who owns VOLUE AS?

EDISON BIDCO AS
VOLUE AS
NOK 61.4m rev. · NOK −35.9m profit

VOLUE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VOLUE AS own?

VOLUE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VOLUE AS

Who owns VOLUE AS?

EDISON BIDCO AS is the largest registered owner, with 100.0%.

What is the revenue of VOLUE AS?

VOLUE AS had revenue of NOK 61.4m in 2024.

Who is the general manager of VOLUE AS?

Arnstein Kjesbu is registered as general manager of VOLUE AS.

Where is VOLUE AS based?

VOLUE 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.