BIZTRAC BETA
Other software publishing

XENETA AS

Org. no. 915736076 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 295.6m
Operating profit NOK −181.2m
Equity NOK 79.5m
Incorporated 2015
Employees 112
Share capital NOK 217,000

Signals

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

XENETA AS is registered as a limited company in Oslo, Oslo with organisation number 915736076. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2015 and has 112 registered employees. Registered share capital is NOK 217,000, divided into 21694667 shares. The company's stated purpose is: “Internettjenester relatert til logistikkaktivitet ved frakt av gods.”. The most recent filed accounts, for the 2024 financial year, show NOK 295.6m in revenue and NOK −181.2m in operating profit.

Key figures · 2024

Revenue
NOK 295.6m
Operating profit
NOK −181.2m
Equity
NOK 79.5m
Est. value
NOK 534.8m

Financial health · 2024

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

Who owns XENETA AS?

ARGO ACQUISITION CO. LIMITED
XENETA AS
NOK 295.6m rev. · NOK −181.2m profit

XENETA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does XENETA AS own?

XENETA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about XENETA AS

Who owns XENETA AS?

ARGO ACQUISITION CO. LIMITED is the largest registered owner, with 15.6%.

What is the revenue of XENETA AS?

XENETA AS had revenue of NOK 295.6m in 2024.

Who is the general manager of XENETA AS?

Patrik Olstad Berglund is registered as general manager of XENETA AS.

Where is XENETA AS based?

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