BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

ONYX CENTERSOURCE AS

Org. no. 883430972 Limited company (AS) Tønsberg Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 543.8m
Operating profit NOK 148.1m
Equity NOK 6.4m
Incorporated 2001
Employees 25
Share capital NOK 1.5m

ONYX CENTERSOURCE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 883430972. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2001 and has 25 registered employees. Registered share capital is NOK 1.5m, divided into 7122955 shares. The company's stated purpose is: “Etablering og drift av internettjenester, herunder e-handel, samt dertil hørende virksomhet og investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 543.8m in revenue and NOK 148.1m in operating profit.

Key figures · 2024

Revenue
NOK 543.8m
Operating profit
NOK 148.1m
Equity
NOK 6.4m
Est. value
NOK 702.5m

Financial health · 2024

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

Who owns ONYX CENTERSOURCE AS?

ONYX NORWAY HOLDING AS
ONYX CENTERSOURCE AS
NOK 543.8m rev. · NOK 148.1m profit

ONYX CENTERSOURCE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ONYX CENTERSOURCE AS er morselskap for 1 datterselskap:

Frequently asked questions about ONYX CENTERSOURCE AS

Who owns ONYX CENTERSOURCE AS?

ONYX NORWAY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ONYX CENTERSOURCE AS?

ONYX CENTERSOURCE AS had revenue of NOK 543.8m in 2024.

Where is ONYX CENTERSOURCE AS based?

ONYX CENTERSOURCE AS has its business address in Tønsberg.

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.