BIZTRAC BETA
Uoppgitt

XANIA COMMERCE GROUP AS

Org. no. 934639375 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −77,000
Equity NOK 109.1m
Incorporated 2024
Share capital NOK 159,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−77k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-12 Aksjekapital registrert 2026-02-12.

XANIA COMMERCE GROUP AS is registered as a limited company in Asker, Akershus with organisation number 934639375. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 159,000, divided into 158680 shares. The company's stated purpose is: “Investering i og forvaltning av aksjer og andre verdipapirer, samt det som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −77,000
Equity
NOK 109.1m
Est. value
NOK 128.2m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.9%
Very good
Equity as a share of total capital

Who owns XANIA COMMERCE GROUP AS?

XANIA GROUP AS
XANIA COMMERCE GROUP AS
· NOK −77,000 profit

XANIA COMMERCE GROUP AS has 2 registered shareholders:

All shareholders and roles →

Which companies does XANIA COMMERCE GROUP AS own?

XANIA COMMERCE GROUP AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

XANIA COMMERCE GROUP AS er morselskap for 42 datterselskaper:

Frequently asked questions about XANIA COMMERCE GROUP AS

Who owns XANIA COMMERCE GROUP AS?

XANIA GROUP AS is the largest registered owner, with 91.4%.

Where is XANIA COMMERCE GROUP AS based?

XANIA COMMERCE GROUP AS has its business address in Nesbru.

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.